Peer-based mobile computing entity management system

ABSTRACT

Various embodiments are directed to systems and methods for engaging a service provider to perform a delivery service to redirect a shipment to be delivered to an alternative intended destination upon receipt of a redirection request. Based on a monitored current location of a last mile delivery vehicle scheduled to deliver the shipment to an initial intended destination, a computing entity monitors the location of available service providers capable of meeting the last mile delivery vehicle to pick up the shipment and transport the shipment to the alternative intended destination. The computing entity may engage one of the service providers by transmitting a signal to a mobile computing entity carried by the service provider and may monitor the service provider&#39;s progress in meeting the last mile delivery vehicle and transporting the shipment to the alternative intended destination.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of prior application Ser. No.15/412,964, filed Jan. 23, 2017, which claims benefit of priority fromProvisional Application Ser. No. 62/437,490, filed on Dec. 21, 2016,which is incorporated herein by reference in its entirety.

BACKGROUND

Generally, shipments/items are delivered to a destination locationidentified at the time the shipment/item is initiated at a shipmentorigin. Often, a shipment/item is given to a carrier at the shipmentorigin and the carrier transports the shipment/item from the shipmentorigin to the destination. The shipment/item may be directed through oneor more carrier sort locations between the shipment origin and thedestination and ultimately, the shipment/item is placed onto a last-miledelivery vehicle at a final sort location for delivery to thedestination location.

Historically, various concepts have been developed enabling ashipment/item to be redirected and thereby delivered to an alternativedestination by directing the shipment/item to an alternative final sortlocation and/or placing the shipment/item onto a different last miledelivery vehicle while at the final sort location. For example, commonlyowned U.S. patent application Ser. No. 13/174,306, filed Jul. 1, 2011describes concepts enabling an intended package recipient to requestthat a shipment/item is redirected and delivered to a particular carrierlocation where the shipment/item is held until the recipient is ready topick-up the shipment/item.

However, shippers and recipients desire additional shipment options tofacilitate final delivery of a shipment/item to a desired location.Accordingly, a need exists for concepts enabling shippers and recipientsto further customize delivery of shipments/items during all stages ofdelivery.

BRIEF SUMMARY

Various embodiments enable shippers and recipients to request variouslocation specific services are performed with respect to one or moreshipments/items. For example, shippers and/or recipients may request toredirect shipments/items to alternative delivery locations selected bythe shipper and/or recipient during the last mile delivery of theshipment/item to an original delivery location. Accordingly, while theshipment/item is on a last mile delivery vehicle for delivery to aninitial intended destination (but before delivery to the initialintended destination), the shipper and/or recipient may request toredirect the shipment/item to an alternative intended destination. Invarious embodiments, the carrier may determine whether the alternativedelivery location satisfies applicable criteria, and may request that aservice provider meet the last mile delivery vehicle to obtain theshipment/item and deliver the shipment/item to the alternative deliverylocation. Accordingly, various embodiments may identify appropriateservice providers available to meet the last mile delivery vehicle andmay identify appropriate meet points and meet times to facilitate theshipment/item handoff without requiring the last mile delivery vehicleto deviate significantly from an assigned route.

Various embodiments are directed to a method for engaging a serviceprovider to perform a location-specific service involving an item. Invarious embodiments, the method comprising steps for: receiving, via thecentral computing entity, a service request corresponding to at leastone item located on a vehicle, wherein the service request identifies arequested service involving the at least one item and wherein the atleast one item is located on a vehicle traversing an assigned vehicleroute; monitoring, via the central computing entity and based at leastin part on location data received from the vehicle, the current locationof the vehicle relative to the assigned vehicle route to identify anuntraversed portion of the assigned vehicle route; monitoring, via thecentral computing entity, the current location of one or more serviceproviders based at least in part on service provider location datareceived in real time from mobile computing entities carried by each ofthe one or more service providers; based at least in part on theidentified untraversed portion of the assigned vehicle route,identifying, via the central computing entity, one or more potentialmeet locations and corresponding potential meet times, wherein thepotential meet locations are located along the untraversed portion ofthe assigned vehicle route and the corresponding potential meet timesare each identified based at least in part on an estimated time ofarrival of the vehicle at the one or more potential meet locations whilethe vehicle travels along the untraversed portion of the assignedvehicle route; comparing, via the central computing entity, the receivedservice provider location data against the one or more potential meetlocations and corresponding meet times to identify one or more eligibleservice providers, wherein the eligible service providers are identifiedas capable of traveling to at least one potential meet location by acorresponding potential meet time; electronically communicating with aservice provider computing entity associated with one of the eligibleservice providers to engage the eligible service provider to perform therequested service for the at least one item; and transmitting, via thecentral computing entity, one or more signals to the vehicle and themobile computing entity carried by the engaged service providerindicating a meet location and corresponding meet time identified as oneof the potential meet locations for which the engaged service provideris capable of traveling to by the corresponding potential meet time.

In various embodiments, the method comprises further steps forgenerating identity verification data to enable verification of theidentity of the service provider at the meet location; and transmittingthe identity verification data to at least one of the delivery vehicleor the service provider computing entity carried by the engaged serviceprovider. Moreover, the identity verification data may be configured toenable a virtual handshake between the delivery vehicle and the serviceprovider computing entity carried by the engaged service provider.

In various embodiments, the method further comprises steps for receivingdata indicating that the item has been transferred to the engagedservice provider; and monitoring the location of the engaged serviceprovider while the engaged service provider transports the item. Invarious embodiments, the meet location may be a predefined stop alongthe delivery route. Moreover, in certain embodiments, transmitting oneor more signals to the delivery vehicle comprises steps for transmittingone or more signals to a mobile computing entity carried by a deliveryvehicle operator associated with the delivery vehicle.

In certain embodiments, monitoring the location of one or more availableservice providers comprises: querying a database of item datacorresponding to a plurality of items to identify characteristics of theat least one item; querying a database of available service providersbased at least in part on a portion of the item data for the at leastone item to identify one or more service providers qualified to performthe requested service involving the at least one item; and monitoringthe location of one or more available service providers qualified toperform the requested service involving the at least one item. Moreover,in certain embodiments, the requested service comprises transporting theat least one item to an alternative intended destination.

Various embodiments are directed to a system for engaging a serviceprovider to perform a location-specific service involving an item. Incertain embodiments, the system comprising one or more memory storageareas and one or more computer processors, the system configured to:receive, via the one or more computer processors, a service requestcorresponding to at least one item located on a vehicle, wherein theservice request identifies a requested service involving the at leastone item and wherein the at least one item is located on a vehicletraversing an assigned vehicle route; monitor, via the one or morecomputer processors and based at least in part on location data receivedfrom the vehicle, the current location of the vehicle relative to theassigned vehicle route to identify an untraversed portion of theassigned vehicle route; monitor, via the one or more computerprocessors, the current location of one or more service providers basedat least in part on service provider location data received in real timefrom mobile computing entities carried by each of the one or moreservice providers; based at least in part on the identified untraversedportion of the assigned vehicle route, identify, via the one or morecomputer processors, one or more potential meet locations andcorresponding potential meet times, wherein the potential meet locationsare located along the untraversed portion of the assigned vehicle routeand the corresponding potential meet times are each identified based atleast in part on an estimated time of arrival of the vehicle at the oneor more potential meet locations while the vehicle travels along theuntraversed portion of the assigned vehicle route; compare, via the oneor more computer processors, the received service provider location dataagainst the one or more potential meet locations and corresponding meettimes to identify one or more eligible service providers, wherein theeligible service providers are identified as capable of traveling to atleast one potential meet location by a corresponding potential meettime; electronically communicate with a service provider computingentity associated with one of the eligible service providers to engagethe eligible service provider to perform the requested service for theat least one item; and transmit, via the one or more computerprocessors, one or more signals to the vehicle and the mobile computingentity carried by the engaged service provider indicating a meetlocation and corresponding meet time identified as one of the potentialmeet locations for which the engaged service provider is capable oftraveling to by the corresponding potential meet time.

In various embodiments, the system may be further configured to generateidentity verification data to enable verification of the identity of theservice provider at the meet location; and transmit the identityverification data to at least one of the delivery vehicle or the serviceprovider computing entity carried by the engaged service provider.Moreover, in various embodiments, the identity verification data isconfigured to enable a virtual handshake between the delivery vehicleand the service provider computing entity carried by the engaged serviceprovider.

In certain embodiments, the system may be further configured to receivedata indicating that the item has been transferred to the engagedservice provider; and monitor the location of the engaged serviceprovider while the engaged service provider transports the item. Infurther embodiments, the meet location is a predefined stop along thedelivery route. Moreover, in certain embodiments, transmitting one ormore signals to the delivery vehicle comprises transmitting one or moresignals to a mobile computing entity carried by a delivery vehicleoperator associated with the delivery vehicle.

In various embodiments, monitoring the location of one or more availableservice providers comprises: querying a database of item datacorresponding to a plurality of items to identify characteristics of theat least one item; querying a database of available service providersbased at least in part on a portion of the item data for the at leastone item to identify one or more service providers qualified to performthe requested service involving the at least one item; and monitoringthe location of one or more available service providers qualified toperform the requested service involving the at least one item. Moreover,in certain embodiments, the requested service comprises transporting theat least one item to an alternative intended destination.

Various embodiments are directed to a computer program productcomprising at least one non-transitory computer-readable storage mediumhaving computer-readable program code portions stored therein. Incertain embodiments, the computer readable program code portions maycomprise: an executable portion configured for receiving a servicerequest corresponding to at least one item located on a vehicle, whereinthe service request identifies a requested service involving the atleast one item and wherein the at least one item is located on a vehicletraversing an assigned vehicle route; an executable portion configuredfor monitoring, based at least in part on location data received fromthe vehicle, the current location of the vehicle relative to theassigned vehicle route to identify an untraversed portion of theassigned vehicle route; an executable portion configured for monitoringthe current location of one or more service providers based at least inpart on service provider location data received in real time from mobilecomputing entities carried by each of the one or more service providers;an executable portion configured for, based at least in part on theidentified untraversed portion of the assigned vehicle route,identifying one or more potential meet locations and correspondingpotential meet times, wherein the potential meet locations are locatedalong the untraversed portion of the assigned vehicle route and thecorresponding potential meet times are each identified based at least inpart on an estimated time of arrival of the vehicle at the one or morepotential meet locations while the vehicle travels along the untraversedportion of the assigned vehicle route; an executable portion configuredfor comparing the received service provider location data against theone or more potential meet locations and corresponding meet times toidentify one or more eligible service providers, wherein the eligibleservice providers are identified as capable of traveling to at least onepotential meet location by a corresponding potential meet time; anexecutable portion configured for electronically communicating with aservice provider computing entity associated with one of the eligibleservice providers to engage the eligible service provider to perform therequested service for the at least one item; and an executable portionconfigured for transmitting one or more signals to the vehicle and themobile computing entity carried by the engaged service providerindicating a meet location and corresponding meet time identified as oneof the potential meet locations for which the engaged service provideris capable of traveling to by the corresponding potential meet time.

In certain embodiments, the computer program product further comprisesan executable portion configured for generating identity verificationdata to enable verification of the identity of the service provider atthe meet location; and an executable portion configured for transmittingthe identity verification data to at least one of the delivery vehicleor the service provider computing entity carried by the engaged serviceprovider. Moreover, in various embodiments, the identity verificationdata is configured to enable a virtual handshake between the deliveryvehicle and the service provider computing entity carried by the engagedservice provider. In certain embodiments, the computer program productfurther comprises an executable portion configured for receiving dataindicating that the item has been transferred to the engaged serviceprovider; and an executable portion configured for monitoring thelocation of the engaged service provider while the engaged serviceprovider transports the item. In certain embodiments, the meet locationis a predefined stop along the delivery route.

In various embodiments, transmitting one or more signals to the deliveryvehicle comprises steps for transmitting one or more signals to a mobilecomputing entity carried by a delivery vehicle operator associated withthe delivery vehicle. Moreover, in certain embodiments, monitoring thelocation of one or more available service providers comprises querying adatabase of item data corresponding to a plurality of items to identifycharacteristics of the at least one item; querying a database ofavailable service providers based at least in part on a portion of theitem data for the at least one item to identify one or more serviceproviders qualified to perform the requested service involving the atleast one item; and monitoring the location of one or more availableservice providers qualified to perform the requested service involvingthe at least one item. Moreover, in certain embodiments, the requestedservice comprises transporting the at least one item to an alternativeintended destination.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 is a diagram of a system that can be used to practice variousembodiments of the present invention.

FIG. 2 is a diagram of an information/data collection device that may beused in association with certain embodiments of the present invention.

FIG. 3 is a schematic of a central computing entity in accordance withcertain embodiments of the present invention.

FIG. 4 is a schematic of a mobile computing entity in accordance withcertain embodiments of the present invention.

FIG. 5 is a flowchart illustrating operations and processes that can beused in accordance with various embodiments of the present invention.

FIG. 6 is an additional flowchart illustrating additional operations andprocesses that can be used in accordance with various embodiments of thepresent invention.

FIG. 7 is a shipment/item flow diagram showing movement of ashipment/item according to various embodiments of the present invention.

DETAILED DESCRIPTION

The present invention will now be described more fully hereinafter withreference to the accompanying drawings, in which some, but not allembodiments of the invention are shown. Indeed, the invention may beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will satisfy applicable legalrequirements. Like numbers refer to like elements throughout.

Various embodiments are directed to concepts enabling a shippeditem/shipment to be redirected from an initial intended destination toan alternative intended destination while the item/shipment is on a lastmile delivery vehicle moving along a route toward the initial intendeddestination, and before the shipment/item is delivered to the initialintended destination. Thus, various embodiments enable item/shipmentredirection during a greater portion of a shipped item/shipment'sdelivery path than previously possible. Accordingly, various embodimentscomprise one or more central computing entities configured to receiverequests from users (e.g., intended recipients and/or shippers) toredirect a shipment/item to an alternative intended destination, toidentify the current location of the shipment/item within the carrier'slogistics network, and to generate appropriate signals to effectredirection of the shipment/item such that the shipment/item is notdelivered to the initial intended destination and is instead redirectedto the alternative intended destination.

In various embodiments, shipment/item redirection is one of a pluralityof potential location-specific services that may be performed via one ormore service providers in accordance with embodiments discussed herein.Accordingly, upon receiving a request for a locations-specific servicefor a particular shipment/item (e.g., shipment/item redirection) in thepossession of the carrier, the central computing entity performs variousprocesses to determine the appropriate methodology for effecting therequested service, based at least in part on the current status and/orlocation of the shipment/item within the carrier's logistics networkand/or the relative location of the alternative intended destinationrelative to the initial intended destination (if applicable). Forexample, upon determining that the shipment/item is being transportedbetween sort locations, or upon determining that the shipment/item iswithin a sort location, the central computing entity may flag electronicinformation/data associated with the shipment (e.g., Package LevelDetail, “PLD”) to inform handling personnel to perform thelocation-specific service (e.g., to redirect the shipment/item towardthe alternative intended destination (e.g., redirect the shipment/itemto a different delivery vehicle)).

Upon determining that the shipment/item is currently on a last miledelivery vehicle for final delivery to the initial intended destinationwhen the service request to redirect a shipment/item is received, thecentral computing entity may compare the relative locations of theinitial intended destination and the alternative intended destination(e.g., by comparing the relative locations stored as mapinformation/data and/or location information/data) to determine the mostappropriate method to redirect the shipment/item. If the initial andalternative intended destinations satisfy applicable criteria (e.g.,within a threshold distance, the request is received before a cutofftime, the initial and alternative intended destinations are not along acommon delivery route, and/or the like), the central computing entitymay utilize location information/data (e.g., GPS information/data) toidentify an appropriate service provider and to generate a request toone or more service providers to retrieve the shipment/item from thelast mile delivery vehicle at a determined meet point and time and todeliver the shipment/item to the alternative intended destination. Forexample, the central computing entity may request a peer-based deliveryservice (e.g., Uber, UberEats, Lyft, GetMe, and/or the like) to assign aparticular service provider to redirect the shipment/item to thealternative intended destination.

As yet other examples, upon receiving the request to redirect theshipment/item to an alternative intended destination, the centralcomputing entity may determine that the originally assigned deliveryvehicle (e.g., the last mile delivery vehicle currently containing theshipment/item) may perform delivery at the alternative intendeddestination, and accordingly the central computing entity may modify theassigned delivery route for the delivery vehicle to effect delivery ofthe shipment/item at the alternative intended destination instead of theinitial intended destination. As yet another example, the centralcomputing entity may determine that the alternative intended destinationand the initial intended destination do not satisfy applicable criteria(e.g., the initial and alternative intended destination locations may bebeyond a threshold distance from one another) and accordingly thecentral computing entity may flag the electronic information/dataassociated with the shipment/item to inform the delivery vehicleoperator to return the shipment/item to a sort facility to redirect theshipment/item to the alternative intended destination.

Accordingly, various embodiments enable redirection of a shipment/itemto an alternative intended destination while the shipment/item is on alast mile delivery vehicle and without requiring the shipment/item to bererouted through a carrier sort location and onto another last miledelivery vehicle at the carrier sort location. By utilizing one or moreservice providers (e.g., peer-based service providers), variousembodiments enable shipment/item redirection during a greater portion ofa shipment travel path between an origin and a destination thanpreviously available. Shipments/items need not follow defined deliveryroutes preassigned to delivery vehicles during the delivery process(which may create significant delays in delivering shipments/items if aredirection request is to be effected), and instead shipments/items maybe redirected from a preassigned delivery route for a particulardelivery vehicle to an alternative intended destination that is notlocated along the preassigned delivery route by providing a serviceprovider to pickup the shipment/item from the delivery vehicle andtransport the shipment/item to the alternative intended destination.

I. Computer Program Products, Methods, and Computing Entities

Embodiments of the present invention may be implemented in various ways,including as computer program products that comprise articles ofmanufacture. A computer program product may include a non-transitorycomputer-readable storage medium storing applications, programs, programmodules, scripts, source code, program code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like (also referred to herein as executable instructions,instructions for execution, program code, and/or similar terms usedherein interchangeably). Such non-transitory computer-readable storagemedia include all computer-readable media (including volatile andnon-volatile media).

In one embodiment, a non-volatile computer-readable storage medium mayinclude a floppy disk, flexible disk, hard disk, solid-state storage(SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solidstate module (SSM)), enterprise flash drive, magnetic tape, or any othernon-transitory magnetic medium, and/or the like. A nonvolatilecomputer-readable storage medium may also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc(DVD), Blu-ray disc (BD), any other non-transitory optical medium,and/or the like. Such a non-volatile computer-readable storage mediummay also include read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory (e.g.,Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC),secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF)cards, Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium may also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), non-volatile random-accessmemory (NVRAM), magnetoresistive random-access memory (MRAM), resistiverandom-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory(SONOS), floating junction gate random access memory (FJG RAM),Millipede memory, racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium mayinclude random access memory (RAM), dynamic random access memory (DRAM),static random access memory (SRAM), fast page mode dynamic random accessmemory (FPM DRAM), extended data-out dynamic random access memory (EDODRAM), synchronous dynamic random access memory (SDRAM), doubleinformation/data rate synchronous dynamic random access memory (DDRSDRAM), double information/data rate type two synchronous dynamic randomaccess memory (DDR2 SDRAM), double information/data rate type threesynchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamicrandom access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM(T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM),dual in-line memory module (DIMM), single in-line memory module (SIMM),video random access memory (VRAM), cache memory (including variouslevels), flash memory, register memory, and/or the like. It will beappreciated that where embodiments are described to use acomputer-readable storage medium, other types of computer-readablestorage media may be substituted for or used in addition to thecomputer-readable storage media described above.

As should be appreciated, various embodiments of the present inventionmay also be implemented as methods, apparatus, systems, computingdevices, computing entities, and/or the like. As such, embodiments ofthe present invention may take the form of an apparatus, system,computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. However, embodiments of the presentinvention may also take the form of an entirely hardware embodimentperforming certain steps or operations.

Embodiments of the present invention are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations may be implemented in the form of a computer programproduct, an entirely hardware embodiment, a combination of hardware andcomputer program products, and/or apparatus, systems, computing devices,computing entities, and/or the like carrying out instructions,operations, steps, and similar words used interchangeably (e.g., theexecutable instructions, instructions for execution, program code,and/or the like) on a computer-readable storage medium for execution.For example, retrieval, loading, and execution of code may be performedsequentially such that one instruction is retrieved, loaded, andexecuted at a time. In some exemplary embodiments, retrieval, loading,and/or execution may be performed in parallel such that multipleinstructions are retrieved, loaded, and/or executed together. Thus, suchembodiments can produce specifically-configured machines performing thesteps or operations specified in the block diagrams and flowchartillustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified instructions, operations, or steps.

II. Exemplary System Architecture

FIG. 1 provides an illustration of a system that can be used inconjunction with various embodiments of the present invention. As shownin FIG. 1, the system may include one or more vehicles 100, one or moremobile computing entities 105, one or more central computing entities110, one or more Global Positioning System (GPS) satellites 115, one ormore location sensors 120, one or more telematics sensors 125, one ormore information/data collection devices 130, one or more networks 135,one or more user computing entities 140 (not shown), and/or the like.Each of the components of the system may be in electronic communicationwith, for example, one another over the same or different wireless orwired networks including, for example, a wired or wireless Personal AreaNetwork (PAN), Local Area Network (LAN), Metropolitan Area Network(MAN), Wide Area Network (WAN), or the like. Additionally, while FIG. 1illustrates certain system entities as separate, standalone entities,the various embodiments are not limited to this particular architecture.

a. Exemplary Vehicle

In various embodiments, the term vehicle 100 is used generically. Forexample, a vehicle 100 may be a manned or an unmanned tractor, truck,car, motorcycle, moped, Segway, bicycle, golf cart, hand truck, cart,trailer, tractor and trailer combination, van, flatbed truck, vehicle,drone, airplane, helicopter, boat, barge, and/or any other form ofobject for moving or transporting people and/or items (e.g., one or morepackages, parcels, bags, containers, loads, crates, items bandedtogether, vehicle parts, pallets, drums, the like, and/or similar wordsused herein interchangeably). In one embodiment, each vehicle 100 may beassociated with a unique vehicle identifier (such as a vehicle ID) thatuniquely identifies the vehicle 100. The unique vehicle ID (e.g.,trailer ID, tractor ID, vehicle ID, and/or the like) may includecharacters, such as numbers, letters, symbols, and/or the like. Forexample, an alphanumeric vehicle ID (e.g., “AS445”) may be associatedwith each vehicle 100. In another embodiment, the unique vehicle ID maybe the license plate, registration number, or other identifyinginformation/data assigned to the vehicle 100. In various embodiments, aservice provider 100 a as discussed herein may be embodied as, comprise,and/or be associated with a vehicle.

FIG. 1 shows one or more computing entities, devices, and/or similarwords used herein interchangeably that are associated with the vehicle100, such as an information/data collection device 130 or othercomputing entities. In general, the terms computing entity, entity,device, system, and/or similar words used herein interchangeably mayrefer to, for example, one or more computers, computing entities,desktop computers, mobile phones, tablets, phablets, notebooks, laptops,distributed systems, gaming consoles (e.g., Xbox, Play Station, Wii),watches, glasses, iBeacons, proximity beacons, key fobs, radio frequencyidentification (RFID) tags, ear pieces, scanners, televisions, dongles,cameras, wristbands, wearable items/devices, items/devices, vehicles,kiosks, input terminals, servers or server networks, blades, gateways,switches, processing devices, processing entities, set-top boxes,relays, routers, network access points, base stations, the like, and/orany combination of devices or entities adapted to perform the functions,operations, and/or processes described herein. FIG. 2 provides a blockdiagram of an exemplary information/data collection device 130 that maybe attached, affixed, disposed upon, integrated into, or part of avehicle 100. The information/data collection device 130 may collecttelematics information/data (including location information/data) andtransmit/send the information/data to the mobile computing entity 105,the central computing entity 110, and/or various other computingentities via one of several communication methods.

In one embodiment, the information/data collection device 130 mayinclude, be associated with, or be in wired or wireless communicationwith one or more processors 200 (various exemplary processors aredescribed in greater detail below), one or more location-determiningdevices or one or more location sensors 120 (e.g., Global NavigationSatellite System (GNSS) sensors), one or more telematics sensors 125,one or more real-time clocks 215, a J-Bus protocol architecture, one ormore electronic control modules (ECM) 245, one or more communicationports 230 for receiving telematics information/data from various sensors(e.g., via a CAN-bus), one or more communication ports 205 fortransmitting/sending information/data, one or more RFID tags/sensors250, one or more power sources 220, one or more information/data radios235 for communication with a variety of communication networks, one ormore memory modules 210, and one or more programmable logic controllers(PLC) 225. It should be noted that many of these components may belocated in the vehicle 100 but external to the information/datacollection device 130.

In one embodiment, the one or more location sensors 120, modules, orsimilar words used herein interchangeably may be one of severalcomponents in wired or wireless communication with or available to theinformation/data collection device 130. Moreover, the one or morelocation sensors 120 may be compatible with GPS satellites 115, such asLow Earth Orbit (LEO) satellite systems, Department of Defense (DOD)satellite systems, the European Union Galileo positioning systems, theChinese Compass navigation systems, Indian Regional Navigationalsatellite systems, and/or the like. This information/data can becollected using a variety of coordinate systems, such as the DecimalDegrees (DD); Degrees, Minutes, Seconds (DMS); Universal TransverseMercator (UTM); Universal Polar Stereographic (UPS) coordinate systems;and/or the like. Alternatively, triangulation may be used in connectionwith a device associated with a particular vehicle and/or the vehicle'soperator and with various communication points (e.g., cellular towers orWi-Fi access points) positioned at various locations throughout ageographic area to monitor the location of the vehicle 100 and/or itsoperator. The one or more location sensors 120 may be used to receivelatitude, longitude, altitude, heading or direction, geocode, course,position, time, and/or speed information/data (e.g., referred to hereinas telematics information/data and further described herein below). Theone or more location sensors 120 may also communicate with the centralcomputing entity 110, the information/data collection device 130, mobilecomputing entity 105, and/or similar computing entities.

As indicated, in addition to the one or more location sensors 120, theinformation/data collection device 130 may include and/or be associatedwith one or more telematics sensors 125, modules, and/or similar wordsused herein interchangeably. For example, the telematics sensors 125 mayinclude vehicle sensors, such as engine, fuel, odometer, hubometer, tirepressure, location, weight, emissions, door, and speed sensors. Thetelematics information/data may include, but is not limited to, speedinformation/data, emissions information/data, RPM information/data, tirepressure information/data, oil pressure information/data, seat beltusage information/data, distance information/data, fuelinformation/data, idle information/data, and/or the like (e.g., referredto herein as telematics information/data). The telematics sensors 125may include environmental sensors, such as air quality sensors,temperature sensors, and/or the like. Thus, the telematicsinformation/data may also include carbon monoxide (CO), nitrogen oxides(NOx), sulfur oxides (SOx), Ethylene Oxide (EtO), ozone (03), hydrogensulfide (H₂S) and/or ammonium (NH4) information/data, and/ormeteorological information/data (e.g., referred to herein as telematicsinformation/data).

In one embodiment, the ECM 245 may be one of several components incommunication with and/or available to the information/data collectiondevice 130. The ECM 245, which may be a scalable and subservient deviceto the information/data collection device 130, may have information/dataprocessing capability to decode and store analog and digital inputs fromvehicle systems and sensors. The ECM 245 may further haveinformation/data processing capability to collect and present telematicsinformation/data to the J-Bus (which may allow transmission to theinformation/data collection device 130), and output standard vehiclediagnostic codes when received from a vehicle's J-Bus-compatibleon-board controllers 240 and/or sensors.

As indicated, a communication port 230 may be one of several componentsavailable in the information/data collection device 130 (or be in or asa separate computing entity). Embodiments of the communication port 230may include an Infrared information/data Association (IrDA)communication port, an information/data radio, and/or a serial port. Thecommunication port 230 may receive instructions for the information/datacollection device 130. These instructions may be specific to the vehicle100 in which the information/data collection device 130 is installed,specific to the geographic area in which the vehicle 100 will betraveling, specific to the function the vehicle 100 serves within afleet, and/or the like. In one embodiment, the information/data radio235 may be configured to communicate with a wireless wide area network(WWAN), wireless local area network (WLAN), wireless personal areanetwork (WPAN), or any combination thereof. For example, theinformation/data radio 235 may communicate via various wirelessprotocols, such as 802.11, general packet radio service (GPRS),Universal Mobile Telecommunications System (UMTS), Code DivisionMultiple Access 2000 (CDMA2000), CDMA2000 1× (1×RTT), Wideband CodeDivision Multiple Access (WCDMA), Time Division-Synchronous CodeDivision Multiple Access (TD-SCDMA), Long Term Evolution (LTE), EvolvedUniversal Terrestrial Radio Access Network (E-UTRAN), Evolution-DataOptimized (EVDO), High Speed Packet Access (HSPA), High-Speed DownlinkPacket Access (HSDPA), IEEE 802.11 (Wi-Fi), 802.16 (WiMAX), ultrawideband (UWB), infrared (IR) protocols, Bluetooth protocols (includingBluetooth low energy (BLE)), wireless universal serial bus (USB)protocols, and/or any other wireless protocol.

b. Exemplary Central Computing Entity

FIG. 3 provides a schematic of a central computing entity 110 accordingto one embodiment of the present invention. In general, the termscomputing entity, entity, device, system, and/or similar words usedherein interchangeably may refer to, for example, one or more computers,computing entities, desktop computers, mobile phones, tablets, phablets,notebooks, laptops, distributed systems, gaming consoles (e.g., Xbox,Play Station, Wii), watches, glasses, iBeacons, proximity beacons, keyfobs, radio frequency identification (RFID) tags, ear pieces, scanners,televisions, dongles, cameras, wristbands, wearable items/devices,items/devices, vehicles, kiosks, input terminals, servers or servernetworks, blades, gateways, switches, processing devices, processingentities, set-top boxes, relays, routers, network access points, basestations, the like, and/or any combination of devices or entitiesadapted to perform the functions, operations, and/or processes describedherein. Such functions, operations, and/or processes may include, forexample, transmitting, receiving, operating on, processing, displaying,storing, determining, creating/generating, monitoring, evaluating,comparing, and/or similar terms used herein interchangeably. In oneembodiment, these functions, operations, and/or processes can beperformed on information/data, content, information, and/or similarterms used herein interchangeably.

As indicated, in one embodiment, the central computing entity 110 mayalso include one or more communications interfaces 320 for communicatingwith various computing entities, such as by communicatinginformation/data, content, information, and/or similar terms used hereininterchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. For instance, the centralcomputing entity 110 may communicate with vehicles 100, mobile computingentities 105, and/or the like.

As shown in FIG. 3, in one embodiment, the central computing entity 110may include or be in communication with one or more processing elements305 (also referred to as processors, processing circuitry, and/orsimilar terms used herein interchangeably) that communicate with otherelements within the central computing entity 110 via a bus, for example.As will be understood, the processing element 305 may be embodied in anumber of different ways. For example, the processing element 305 may beembodied as one or more complex programmable logic devices (CPLDs),microprocessors, multi-core processors, coprocessing entities,application-specific instruction-set processors (ASIPs), and/orcontrollers. Further, the processing element 305 may be embodied as oneor more other processing devices or circuitry. The term circuitry mayrefer to an entirely hardware embodiment or a combination of hardwareand computer program products. Thus, the processing element 305 may beembodied as integrated circuits, application specific integratedcircuits (ASICs), field programmable gate arrays (FPGAs), programmablelogic arrays (PLAs), hardware accelerators, other circuitry, and/or thelike. As will therefore be understood, the processing element 305 may beconfigured for a particular use or configured to execute instructionsstored in volatile or non-volatile media or otherwise accessible to theprocessing element 305. As such, whether configured by hardware orcomputer program products, or by a combination thereof, the processingelement 305 may be capable of performing steps or operations accordingto embodiments of the present invention when configured accordingly.

In one embodiment, the central computing entity 110 may further includeor be in communication with non-volatile media (also referred to asnon-volatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In one embodiment, thenon-volatile storage or memory may include one or more non-volatilestorage or memory media 310 as described above, such as hard disks, ROM,PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks,CBRAM, PRAM, FeRAM, RRAM, SONOS, racetrack memory, and/or the like. Aswill be recognized, the non-volatile storage or memory media may storedatabases, database instances, database management system entities,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like. The termdatabase, database instance, database management system entity, and/orsimilar terms used herein interchangeably may refer to a structuredcollection of records or information/data that is stored in acomputer-readable storage medium, such as via a relational database,hierarchical database, and/or network database.

In one embodiment, the central computing entity 110 may further includeor be in communication with volatile media (also referred to as volatilestorage, memory, memory storage, memory circuitry and/or similar termsused herein interchangeably). In one embodiment, the volatile storage ormemory may also include one or more volatile storage or memory media 315as described above, such as RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM,DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cachememory, register memory, and/or the like. As will be recognized, thevolatile storage or memory media may be used to store at least portionsof the databases, database instances, database management systementities, information/data, applications, programs, program modules,scripts, source code, object code, byte code, compiled code, interpretedcode, machine code, executable instructions, and/or the like beingexecuted by, for example, the processing element 305. Thus, thedatabases, database instances, database management system entities,information/data, applications, programs, program modules, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like may be used tocontrol certain aspects of the operation of the central computing entity110 with the assistance of the processing element 305 and operatingsystem.

As indicated, in one embodiment, the central computing entity 110 mayalso include one or more communications interfaces 320 for communicatingwith various computing entities, such as by communicatinginformation/data, content, information, and/or similar terms used hereininterchangeably that can be transmitted, received, operated on,processed, displayed, stored, and/or the like. For instance, the centralcomputing entity 110 may communicate with computing entities orcommunication interfaces of the vehicle 100, mobile computing entities105, and/or the like.

Such communication may be executed using a wired information/datatransmission protocol, such as fiber distributed information/datainterface (FDDI), digital subscriber line (DSL), Ethernet, asynchronoustransfer mode (ATM), frame relay, information/data over cable serviceinterface specification (DOCSIS), or any other wired transmissionprotocol. Similarly, the central computing entity 110 may be configuredto communicate via wireless external communication networks using any ofa variety of protocols, such as GPRS, UMTS, CDMA2000, 1×RTT, WCDMA,TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IRprotocols, Bluetooth protocols, USB protocols, and/or any other wirelessprotocol. Although not shown, the central computing entity 110 mayinclude or be in communication with one or more input elements, such asa keyboard input, a mouse input, a touch screen/display input, audioinput, pointing device input, joystick input, keypad input, and/or thelike. The central computing entity 110 may also include or be incommunication with one or more output elements (not shown), such asaudio output, video output, screen/display output, motion output,movement output, and/or the like.

As will be appreciated, one or more of the central computing entity's110 components may be located remotely from other central computingentity 110 components, such as in a distributed system. Furthermore, oneor more of the components may be combined and additional componentsperforming functions described herein may be included in the centralcomputing entity 110. Thus, the central computing entity 110 can beadapted to accommodate a variety of needs and circumstances.

c. Exemplary Mobile Computing Entity

FIG. 4 provides an illustrative schematic representative of a mobilecomputing entity 105 that can be used in conjunction with embodiments ofthe present invention. In one embodiment, the mobile computing entities105 may include one or more components that are functionally similar tothose of the central computing entity 110 and/or as described below. Aswill be recognized, mobile computing entities 105 can be operated byvarious parties, including operators of vehicles 100. As shown in FIG.4, a mobile computing entity 105 can include an antenna 412, atransmitter 404 (e.g., radio), a receiver 406 (e.g., radio), and aprocessing element 408 that provides signals to and receives signalsfrom the transmitter 404 and receiver 406, respectively.

The signals provided to and received from the transmitter 404 and thereceiver 406, respectively, may include signaling information/data inaccordance with an air interface standard of applicable wireless systemsto communicate with various entities, such as vehicles 100, centralcomputing entities 110, and/or the like. In this regard, the mobilecomputing entity 105 may be capable of operating with one or more airinterface standards, communication protocols, modulation types, andaccess types. More particularly, the mobile computing entity 105 mayoperate in accordance with any of a number of wireless communicationstandards and protocols. In a particular embodiment, the mobilecomputing entity 105 may operate in accordance with multiple wirelesscommunication standards and protocols, such as GPRS, UMTS, CDMA2000,1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX,UWB, IR protocols, Bluetooth protocols, USB protocols, and/or any otherwireless protocol.

Via these communication standards and protocols, the mobile computingentity 105 can communicate with various other entities using conceptssuch as Unstructured Supplementary Service information/data (USSD),Short Message Service (SMS), Multimedia Messaging Service (MMS),Dual-Tone Multi-Frequency Signaling (DTMF), and/or Subscriber IdentityModule Dialer (SIM dialer). The mobile computing entity 105 can alsodownload changes, add-ons, and updates, for instance, to its firmware,software (e.g., including executable instructions, applications, programmodules), and operating system.

According to one embodiment, the mobile computing entity 105 may includelocation determining aspects, devices, modules, functionalities, and/orsimilar words used herein interchangeably. For example, the mobilecomputing entity 105 may include outdoor positioning aspects, such as alocation module adapted to acquire, for example, latitude, longitude,altitude, geocode, course, direction, heading, speed, UTC, date, and/orvarious other information/data. In one embodiment, the location modulecan acquire information/data, sometimes known as ephemerisinformation/data, by identifying the number of satellites in view andthe relative positions of those satellites. The satellites may be avariety of different satellites, including LEO satellite systems, DODsatellite systems, the European Union Galileo positioning systems, theChinese Compass navigation systems, Indian Regional Navigationalsatellite systems, and/or the like. Alternatively, the locationinformation/data may be determined by triangulating the mobile computingentity's 105 position in connection with a variety of other systems,including cellular towers, Wi-Fi access points, and/or the like.Similarly, the mobile computing entity 105 may include indoorpositioning aspects, such as a location module adapted to acquire, forexample, latitude, longitude, altitude, geocode, course, direction,heading, speed, time, date, and/or various other information/data. Someof the indoor aspects may use various position or location technologiesincluding RFID tags, indoor beacons or transmitters, Wi-Fi accesspoints, cellular towers, nearby computing devices (e.g., smartphones,laptops) and/or the like. For instance, such technologies may includeiBeacons, Gimbal proximity beacons, BLE transmitters, Near FieldCommunication (NFC) transmitters, and/or the like. These indoorpositioning aspects can be used in a variety of settings to determinethe location of someone or something to within inches or centimeters.

The mobile computing entity 105 may also comprise a user interface (thatcan include a display 416 coupled to a processing element 408) and/or auser input interface (coupled to a processing element 408). For example,the user interface may be an application, browser, user interface,dashboard, webpage, and/or similar words used herein interchangeablyexecuting on and/or accessible via the mobile computing entity 105 tointeract with and/or cause display of information. The user inputinterface can comprise any of a number of devices allowing the mobilecomputing entity 105 to receive information/data, such as a keypad 418(hard or soft), a touch display, voice/speech or motion interfaces,scanners, readers, or other input device. In embodiments including akeypad 418, the keypad 418 can include (or cause display of) theconventional numeric (0-9) and related keys (#, *), and other keys usedfor operating the mobile computing entity 105 and may include a full setof alphabetic keys or set of keys that may be activated to provide afull set of alphanumeric keys. In addition to providing input, the userinput interface can be used, for example, to activate or deactivatecertain functions, such as screen savers and/or sleep modes. Throughsuch inputs the mobile computing entity can collect contextualinformation/data as part of the telematics information/data.

The mobile computing entity 105 can also include volatile storage ormemory 422 and/or non-volatile storage or memory 424, which can beembedded and/or may be removable. For example, the non-volatile memorymay be ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards,Memory Sticks, CBRAM, PRAM, FeRAM, RRAM, SONOS, racetrack memory, and/orthe like. The volatile memory may be RAM, DRAM, SRAM, FPM DRAM, EDODRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM,VRAM, cache memory, register memory, and/or the like. The volatile andnon-volatile storage or memory can store databases, database instances,database management system entities, information/data, applications,programs, program modules, scripts, source code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like to implement the functions of the mobile computingentity 105.

In various embodiments, the mobile computing entity 105 may comprise oneor more payment processing entities, such as one or more magnetic cardreaders, one or more NFC readers, one or more chipped-card readers,and/or the like. The mobile computing entity 105 may be configured toreceive data from a central computing entity 110 indicative of an amountto be paid (e.g., an amount owed for one or more services, products,and/or the like), and may be configured to transmit payment data to thecentral computing entity 110 once received from a customer. In variousembodiments, the mobile computing entity 105 may be configured toprocess payments locally (e.g., based on transmissions with one or morebanking institutions to obtain payment approval for various creditaccounts, debit accounts, and/or the like), however, in certainembodiments, the mobile computing entity 105 may be configured totransmit unprocessed payment information to the central computing entity110 for processing. In various embodiments, the mobile computing entity105 may be configured to encrypt payment information received from acustomer. The encrypted payment information may be stored locally (e.g.,temporarily) and/or the encrypted payment information may be transmittedto the central computing entity 110. In various embodiments, the centralcomputing entity 110 may store an encryption key configured to enablethe central computing entity 110 to decrypt received payment informationprior to processing the same. However, in various embodiments, themobile computing entity 105 may be configured to generate and/ortransmit an encryption key to the central computing entity 110. Invarious embodiments, the encryption key may be provided to the centralcomputing entity 110 in a separate transmission from the encryptedpayment information. However, in certain embodiments, the encryptedpayment information and the encryption key may be transmitted in asingle transmission.

d. Exemplary User Computing Entity

In one embodiment, the user computing entities 140 may each include oneor more components that are functionally similar to those of the centralcomputing entity 110 and/or the mobile computing entity 105. Forexample, in one embodiment, each of the user computing entities 140 mayinclude: (1) a processing element that communicates with other elementsvia a system interface or bus; (2) a user interface; (3) transitory andnon-transitory memory; and (4) a communications interface. As previouslynoted, the user computing entity 140 may comprise a user interface. Forexample, the user interface may be an application, browser, userinterface, dashboard, webpage, and/or similar words used hereininterchangeably executing on and/or accessible via the user computingentity 140 to interact with and/or cause display of information/datafrom the central computing entity 110 and/or the mobile computing entity105, as described herein. These architectures are provided for exemplarypurposes only and are not limiting to the various embodiments.

e. Exemplary Service Provider Computing Entity

In various embodiments, a service provider computing entity may beembodied as a mobile computing entity 105, a user computing entity,and/or the like. The service provider computing entity may be associatedwith a service provider, which may provide one or more location-specificservices for one or more shipments/item (e.g., transportation servicesfrom a last mile delivery vehicle 100 to an alternative intendeddestination), as discussed in greater detail herein. The serviceprovider computing entity may facilitate selection of a service providerfor a location-specific service/task by providing locationinformation/data indicative of the current location of the serviceprovider (e.g., determined based on a location determining aspectincorporated in the service provider computing entity) and/oravailability information/data. The location information/data and/oravailability information/data may be provided from the service providercomputing entity in real-time, such that the central computing entity110 uses current and/or dynamic information/data associated with aservice provider when selecting a service provider.

Accordingly, the service provider computing entity may be configured toperform one or more functions to facilitate coordination of performanceof a location-specific service, which may comprise a handoff of ashipment/item to the service provider, navigation and tracking of theservice provider (and the shipment/item) as the service provider movesto the alternative intended destination, and verification of theidentity of the service provider and that the service providersuccessfully delivers the shipment/item to the alternative intendeddestination. Such functionality may be performed by a software program(e.g., application) operating on the service provider computing entity.The software program may be configured to access one or more firmwareand/or hardware features of the service provider computing entity, suchas a location determining feature (e.g., a GPS device), a securityfeature (e.g., a fingerprint reader), a camera, and/or the like.

In various embodiments, the service provider computing entity may beconfigured to communicate with a central computing entity 110 and/or athird party computing entity (e.g., a peer based management computingentity). The service provider computing entity may be configured totransmit information/data indicative of the current status and/oravailability of the service provider (e.g., on duty and available, onduty and busy, off duty, and/or the like) such that the centralcomputing entity 110 (and/or third party computing entity) may determinewhether the service provider is available to perform a location-specificservice (e.g., to transport a shipment/item). In various embodiments,the service provider computing entity may be configured to update theservice provider status upon receipt of user input from the serviceprovider, and/or automatically based at least in part on a predeterminedavailability schedule and/or based on information/data indicatingwhether the service provider is currently assigned to a particular task(e.g., delivering a shipment/item).

Moreover, the service provider computing entity may be configured toprovide location information/data indicative of its current location tothe service provider computing entity 110 (and/or third party computingentity). In various embodiments, the service provider computing entitymay be configured to provide the location information/data only whilethe service provider is available and/or performing a task inassociation with the central computing entity. For example, the serviceprovider computing entity may be configured to share locationinformation/data (e.g., generated by a location determining aspect, suchas a GPS device) with the central computing entity 110 and/or thirdparty computing entity only while the service provider status is set to“On Duty—Available,” “On Duty—Busy,” and/or the like. In suchembodiments, the service provider computing entity may not sharelocation information/data with the central computing entity when theservice provider is unavailable or otherwise not working with thecentral computing entity (e.g., when the service provider status is setto “Off Duty”). As will be discussed in greater detail herein, thelocation information/data shared with the central computing entity 110while the service provider is available may be utilized to determinewhether the service provider is eligible to perform a location-specificservice (e.g., delivery of a shipment/item) and/or may be utilized totrack the location of the service provider (e.g., as a proxy for thelocation of a shipment/item carried by the service provider). In certainembodiments, the service provider computing entity may be configured tocontinuously and/or periodically transmit location information/dataindicative of the current location of the service provider computingentity to the central computing entity. For example, the serviceprovider computing entity may continuously provide updated locationinformation/data to the central computing entity while the serviceprovider is transporting a shipment/item to an alternative intendeddestination.

In various embodiments, the central computing entity 110 (and/or a thirdparty computing entity) may be configured to provide and/or transmit oneor more notifications to the service provider computing entity relatingto tasks, deliveries, and/or the like assigned to the service providerby the central computing entity 110. For example, the service providercomputing entity may be configured to generate, provide, transmit,and/or display a notification to the service provider upon receipt ofinformation/data from the central computing entity indicating that theservice provider has been selected to perform a location specificservice. In various embodiments, the service provider computing entitymay be configured to receive user input indicating whether the serviceprovider is willing to accept the assigned task, and to transmit aresponse to the central computing entity 110 indicating whether theservice provider accepts the task. In such embodiments, the centralcomputing entity 110 (and/or third party computing entity) may transmita service request notification to the service provider computing entityrequesting input indicating whether the service provider is willing toaccept the service request. In various embodiments, the service providercomputing entity may be configured to automatically transmit a responseto the central computing entity 110 if no user input is received withina predefined time period after receipt of the notification. For example,if no user input is received by the service provider computing entityprior to the expiration of a predefined period of time after receipt ofa notification indicating the service provider has been assigned to aparticular task, the service provider computing entity may be configuredto transmit a response indicating that the service provider has rejectedthe task. As yet another example, the service provider computing entitymay be configured to automatically transmit a response indicating thatthe service provider has accepted the task after the expiration of apredefined period of time.

Moreover, as will be discussed in greater detail herein, the serviceprovider computing entity may be configured to perform one or moreservice provider identity verification processes, for example, during ashipment/item handoff. As will be discussed herein, the service providercomputing entity may be utilized to verify the identity of a serviceprovider scheduled to perform a location-specific task, such asdelivering a shipment/item from a last mile delivery vehicle 100 to analternative destination location. For example, the service providercomputing entity may be configured to generate and/or receive one ormore identity verification data, such as verification codes (e.g.,barcodes, QR codes, Maxicodes, alphanumeric strings, symbols, and/or thelike), to perform a virtual handshake with one or more additionalcomputing entities (e.g., a mobile computing entity carried by a lastmile delivery vehicle operator), and/or the like.

In various embodiments, the service provider computing entity may beconfigured to facilitate delivery verifications by the service provider.For example, the service provider computing entity may be configured toaccept input (e.g., user input) indicating that the service providerdelivered the shipment/item to the alternative intended destination. Invarious embodiments, the service provider computing entity may beconfigured to verify the delivery of the shipment/item based on one ormore delivery verification criteria. For example, the service providercomputing entity may be configured to verify the location of the serviceprovider computing entity relative to the location of the alternativeintended destination (e.g., based on location information/data, such asGPS signals), may receive user input from the service providerindicating that the shipment/item was delivered, may receivephotographic input indicating that shipment/item was delivered, and/orthe like. In various embodiments, the service provider computing entitymay be configured to utilize a plurality of delivery verificationcriteria. For example, the service provider computing entity may beconfigured to determine the location of the service provider computingentity relative to the location of the alternative destination locationat the time user input (or other input) is received to indicate that theshipment/item was delivered.

As yet other embodiments, the service provider computing entity may beconfigured to receive image input (e.g., via a camera on the serviceprovider computing entity) of one or more aspects of the alternativeintended destination to verify that the service provider visited thealternative intended destination. For example, the service providercomputing entity may instruct the service provider to photograph astreet number associated with the alternative intended destination, adoor associated with the service provider computing entity, and/or thelike. As yet another example, the service provider computing entity maybe configured to instruct the service provider to take a screenshot ofthe service provider computing entity while the service providercomputing entity displays an image of the shipment/item at thealternative intended destination and a map display showing the currentlocation of the service provider computing entity at the alternativeintended destination.

As yet another example, the service provider computing entity may beconfigured to capture a signature of an intended recipient while theservice provider is delivering the shipment/item at the alternativeintended destination. The service provider computing entity may beconfigured to capture an image of the intended recipient's signature(e.g., via a camera, via writing on an input device of the serviceprovider computing entity, and/or the like).

The service provider computing entity may be configured to transmit thedelivery verification information/data to the central computing entity(e.g., directly and/or via a third party computing entity). As discussedherein, the central computing entity may be configured to store thedelivery verification information/data in the PLD information/datacorresponding to the delivered shipment/item, and/or to transmitinformation/data to the service provider computing entity indicating theservice provider has completed the delivery task.

Like the described mobile computing entity 105, the service providercomputing entity may comprise one or more payment processing entities,such as one or more magnetic card readers, one or more NFC readers, oneor more chipped-card readers, and/or the like. In various embodiments,the service provider computing entity may comprise one or more paymentprocessing algorithms (such as encryption algorithms) as a portion of acomputer program stored on the service provider computing entity. Forexample, the computer program product enabling communications betweenthe service provider computing entity and the central computing entity110 may additionally comprise features for processing payments receivedfrom various customers.

III. Exemplary System Operation

Reference will now be made to FIGS. 5-7. FIGS. 5-6 are flowchartsillustrating operations and processes that can be used in accordancewith various embodiments of the present invention and FIG. 7 is aschematic diagram illustrating movement of a shipment/item between anorigin and an alternative intended destination indicated while theshipment/item is in the possession of a carrier and en route to aninitial intended destination.

a. Shipment/Item Redirection Generally

With reference initially to FIG. 5, the carrier receives a shipment/itemat a shipment/item origin as indicated at Block 501. For example, thecarrier may receive the shipment/item by picking up the shipment/itemfrom the shipment/item origin (e.g., a business, a residence, a drop box(e.g., a carrier operated drop box and/or a third-party drop box),and/or the like), by receiving the shipment/item at a carrier facility(e.g., a carrier operated store-front, a sort location, and/or thelike), and/or the like. When the shipment/item is initially received,the shipment/item may be destined for a particular initial intendeddestination. For example, the initial intended destination may be aspecific deliverable point (e.g., a street address, a post office box,and/or the like), a particular region identified by a region identifier(e.g., a city identified by a city name, a specific region identified bya zip code, a specific delivery route, and/or the like). For example, inthe latter embodiments, the shipment/item may be shipped to a particularregion with the intent that the shipment/item is redirected to adeliverable address while the shipment/item is en route to theparticular region and/or after the shipment/item has arrived at acarrier facility associated with the particular region. As a specificexample, one or more shipments/items may be shipped to a particularregion as discussed in co-pending U.S. patent application Ser. No.14/859,766, filed on Sep. 21, 2015, the entirety of which isincorporated herein by reference in its entirety.

Upon receipt of the shipment/item at the origin, the carrier may begintransporting the shipment/item to the initial intended destination, asindicated at Block 502. In various embodiments, a central computingentity 110 may receive shipping information/data corresponding to theshipment/item and may store the shipping information/data in one or morememory storage areas (e.g., databases) as PLD information/data for theshipment/item. For example, the PLD information/data may compriseinformation/data identifying the shipment/item origin, the shipper, theintended recipient, the initial intended destination, a service level(e.g., Ground, Next Day Air, 2-Day Air, and/or the like). Moreover, invarious embodiments, the central computing entity 110 may generateadditional information/data to be stored as PLD information/data for theshipment/item. For example, the central computing entity 110 maygenerate a shipment identifier (e.g., a tracking number), one or moresort instructions/routing instructions, and/or the like. Moreover, invarious embodiments, the PLD information/data may comprise trackinginformation/data for the shipment/item (e.g., dynamic trackinginformation/data). In various embodiments, the tracking information/datamay be updated each time additional tracking information becomesavailable for the shipment/item (e.g., each time the shipment/item isscanned at a sort location) and/or the tracking information/data may becontinuously updated to reflect a precise location of the shipment/item(e.g., GPS coordinates, current street address of the shipment/item,and/or the like).

Moreover, transporting the shipment/item from the origin to the initialintended destination may comprise transporting the shipment/item toand/or between one or more intermediate sort locations (e.g., carriersort locations) between the origin and the initial intended destination,and/or transporting the shipment/item to a final sort location where theshipment/item is loaded onto a last mile delivery vehicle for finaldelivery to the initial intended destination location.

With reference again to FIG. 5, the central computing entity 110 may beconfigured to determine whether a request to redirect the shipment/itemfrom the initial intended destination to an alternative intendeddestination (and/or other service requests to perform location-specificservices for a shipment/item) is received as indicated at Block 503. Thecentral computing entity 110 may be configured to receive such requestsas “push” requests that cause the central computing entity 110 toperform one or more tasks as discussed herein, and/or the centralcomputing entity 110 may periodically and/or continuously check todetermine whether any requests have been received (e.g., “pull”requests). If no shipment redirection requests are received, theshipment/item proceeds along a carrier defined (e.g., central computingentity 110 defined) route to be delivered to the initial intendeddestination, as indicated at Block 506.

In various embodiments, the shipment redirection requests may bereceived from one or more user computing entities (e.g., operated by anintended shipment/item recipient and/or a shipper). The shipmentredirection requests may be transmitted to the central computing entity110, for example, via one or more networks (e.g., wired and/or wirelessnetworks), such as the Internet. In various embodiments, the shipmentredirection requests may be received via a carrier portal accessible bythe one or more user computing entities (e.g., a website accessible viaa web browser on the one or more user computing entities, a portalaccessible via one or more dedicated computer programs (e.g.,applications) operating on one or more user computing entities, and/orthe like). In various embodiments, a shipment redirection request mayidentify one or more shipments/items for redirection (e.g., byindicating corresponding shipment/item identifiers), an alternativeintended destination for the shipments/items (e.g., a deliverable pointidentified by an address, a post office box, and/or the like), and/orthe like. In various embodiments, the shipment redirection request mayadditionally identify a requested delivery date and/or time for theshipments/items at the one or more alternative intended destinations,and/or the like.

If a shipment redirect request (and/or another location-specific servicerequest) is received by the central computing entity 110, the centralcomputing entity 110 may proceed to determine how to effect therequested shipment/item redirect to ensure the shipment/item isdelivered to the alternative destination location. As indicated at Block504, the central computing entity 110 may be configured to determine thecurrent status of the shipment/item and/or the location of theshipment/item along the logistics route between the shipment origin andthe shipment initial intended destination. For example, the centralcomputing entity 110 may query the one or more memory storage areasstoring PLD information/data corresponding to a plurality ofshipments/items to determine the current status of the shipment/item. Asa specific example, the central computing entity 110 may be configuredto query the tracking information/data for the shipment/item storedwithin the PLD information/data for the shipment/item to determine thecurrent status and/or location of the shipment/item. In variousembodiments, the central computing entity 110 may be configured torecognize various information/data types (e.g., word strings,information/data identifiers, and/or the like) to determine the currentstatus and/or location of the shipment/item. For example, the centralcomputing entity 110 may be configured to recognize trackinginformation/data of “OUT FOR DELIVERY” as indicating that theshipment/item is already loaded onto a last mile delivery vehicle thatis traversing an assigned delivery route to deliver the shipment/item tothe initial intended destination. As yet another example, the centralcomputing entity 110 may be configured to recognize specific locationidentifiers within the tracking information/data as specific sortlocations (e.g., the central computing entity 110 may recognize“ATLANTA, GA” as indicating that the shipment/item is at a sort locationin Atlanta, Ga., but the shipment/item is not yet on a vehicle fordelivery to the initial intended destination location).

In various embodiments, the central computing entity 110 may beconfigured to determine that additional information is needed to make aninformed decision regarding the current status and/or location of theshipment/item after querying the tracking information/data for theshipment/item. Accordingly, the central computing entity 110 may beconfigured to query one or more additional databases and/or otherinformation/data sources to determine the current location and/or statusof a particular shipment/item. For example, the central computing entity110 may be configured to obtain more detailed information/data regardingthe current status of a particular shipment/item if the trackinginformation/data does not provide sufficient detail to determine anappropriate methodology for redirecting a shipment/item (and/orperforming another location-specific service for the shipment/item). Forexample, upon determining that a shipment/item is on a last miledelivery vehicle traversing an assigned delivery route, the centralcomputing entity 110 may query one or more additional databases todetermine the identity of the delivery vehicle containing theshipment/item and/or to determine the current location of the deliveryvehicle along the assigned route. For example, the central computingentity 110 may retrieve precise location information/data for theshipment/item (e.g., GPS coordinates) and/or route progressinformation/data identifying scheduled stops made by the deliveryvehicle (e.g., shipment/item delivery and/or pick-up stops) to determinewhere the delivery vehicle is located along the assigned route. As aspecific example that will be discussed herein, the central computingentity 110 may be configured to determine whether the delivery vehiclehas already passed a requested alternative intended destination (alongthe assigned delivery route) but has not yet reached the initialintended destination in instances in which the initial and alternativeintended destinations are along the same delivery route.

With reference again to FIG. 5, upon determining that the redirectrequest is received before the corresponding shipments/items are placedonto a last mile delivery vehicle for delivery to the initial intendeddestination (as indicated at Block 504), the central computing entity110 may redirect the shipment/item to the appropriate sort locationand/or last mile delivery vehicle to effect delivery to the alternativeintended destination, as indicated at Block 507. For example, thecentral computing entity 110 may update the PLD information/datacorresponding to the shipment/item to reflect the alternative intendeddestination. The central computing entity 110 may additionally generatean electronic flag to be associated with the PLD information/data forthe shipment/item to inform appropriate personnel that the intendeddestination for the shipment/item has changed. Moreover, in variousembodiments, the generated flag may cause one or more computing entitiesto print a new and/or replacement delivery label to be placed onto theshipment/item when the one or more computing entities received PLDinformation/data corresponding to the shipment/item. For example, when aparticular computing entity operated by carrier sort personnel scans anexisting shipment label on the shipment/item, the central computingentity 110 may transmit the updated PLD information/data and thecorresponding flag to the particular computing entity, which may causethe particular computing entity (or an associated computing entity) toprint a replacement shipping label for the shipment/item to indicatethat the shipment/item is to be delivered to the alternative intendeddestination. The carrier may thereafter transport the shipment/item tothe appropriate last mile delivery vehicle to effect final delivery tothe alternative intended destination.

In instances in which the alternative intended destination and theinitial intended destination are located along a common delivery routeserviced by a common delivery vehicle, the shipment/item may be placedonto the last mile delivery vehicle and ultimately delivered to thealternative intended destination. In instances in which the alternativeintended destination is serviced by last mile delivery vehiclesoriginating from a final sort location shared with a last mile deliveryvehicle servicing the initial intended destination, the carrier maydirect the shipment/item to the appropriate last mile delivery vehiclewithin the shared sort location to effect delivery to the alternativeintended destination. In instances in which the alternative intendeddestination is serviced by a last mile delivery vehicle that operatesfrom a different sort facility than the last mile delivery vehicle thatservices the initial intended destination, the carrier may transport theshipment/item to the appropriate sort location and ultimately to theappropriate last mile delivery vehicle to effect delivery to thealternative intended destination.

Referring again to FIG. 5, upon determining that the shipment/item hasalready been placed onto the last mile delivery vehicle for delivery tothe initial intended destination when the redirection request isreceived, the central computing entity 110 may perform one or moreprocesses as indicated in FIG. 6 and discussed herein (as shown at Block505 of FIG. 5).

b. Shipment/Item Redirection after Loading onto a Last Mile DeliveryVehicle

With reference now to FIGS. 5 and 6, various embodiments provide systemsand methods for redirecting shipments/items to alternative destinationlocations (or otherwise enabling location-specific services to beperformed for a shipment/item) after the shipments/items are on a lastmile delivery vehicle for final delivery to an initial intendeddestination location.

As discussed above and as illustrated in FIG. 6, a carrier transports ashipment/item from an origin location 701, through the carrier'stransportation network, and to a final sort location 702 where theshipment/item is placed on a last mile delivery vehicle 100 fordelivery. As discussed herein, the shipment/item is originally placedonto the last mile delivery vehicle 100 scheduled to traverse anassigned delivery route (illustrated schematically as the dashed arrows)and ultimately to deliver the shipment/item to the initial intendeddestination 703, as indicated at Block 601 of FIG. 6.

As discussed herein, the central computing entity 110 may receive arequest to redirect the shipment/item to an alternative intendeddestination 704 after the shipment/item is already loaded onto the lastmile delivery vehicle assigned to deliver shipment/item to the initialintended destination 703, as shown in Blocks 503-505 of FIG. 5 and Block602 of FIG. 6.

In various embodiments, upon receipt of a request to redirect ashipment/item that is already on a last mile delivery vehicle for finaldelivery to an initial intended destination 703, the central computingentity 110 may be configured to determine whether the received requestsatisfies applicable criteria to enable redirection of the shipment/itemand, if redirection is possible, to determine an appropriate methodologyfor redirecting the shipment/item to the alternative intendeddestination 704.

1. Determining whether Redirection Request Satisfies Applicable Criteria

In various embodiments, the central computing entity 110 may beconfigured to determine whether redirection of the shipment/item (and/orother requested location specific services) is available based at leastin part on the request to redirect the shipment/item. In variousembodiments, the central computing entity 110 may be configured todetermine that redirection of a shipment/item may be available when therequest to redirect the shipment item satisfies one or more time-basedcriteria. For example, redirection may only be available if the requestto redirect the shipment/item is received before a predefined time onthe date of expected delivery of the shipment/item to the initialintended destination 703 (e.g., 2:00 PM), if the request to redirect theshipment/item is received more than a predefined time period prior toestimated delivery of the shipment/item to the initial intendeddestination 703 (e.g., 30 minutes before the estimated delivery time),and/or the like.

Moreover, in various embodiments, the central computing entity 110 maybe configured to determine that redirection of a shipment/item (or otherlocation-specific services) may be available when the service request toredirect the shipment/item satisfies one or more location-basedcriteria. For example, redirection may only be available if the requestto redirect the shipment/item identifies an alternative intendeddelivery location 704 that is within a threshold distance from theinitial intended destination 703, is outside of a threshold distancefrom the initial destination 703, is within a defined geographical area(e.g., encompassing the initial intended destination 703), and/or thelike.

In certain embodiments, applicable location-based criteria may beidentified based at least in part on a determination that the request toredirect the shipment/item satisfies one or more of a plurality oftime-based criteria. For example, requests to redirect a shipment/itemthat satisfy a first time-based criteria may be subject to a firstlocation-based criteria, and requests to redirect a shipment/item thatdo not satisfy the first time-based criteria may be subject to a secondlocation-based criteria.

In certain embodiments, a central computing entity 110 may be configuredto determine whether one or more shipments/items are eligible forshipment redirection and/or other location-based services. For example,the PLD information/data corresponding to various shipments/items maycomprise information/data indicating whether the shipment/item iseligible for shipment redirection. In various embodiments, a shipperand/or intended recipient may be configured to provide information/datato the central computing entity 110 (e.g., from one or more usercomputing entities) indicating whether various shipments/items areeligible for shipment redirection. In yet other embodiments, the centralcomputing entity 110 may be configured to determine whether theshipment/item satisfies one or more shipment/item-based criteria toestablish eligibility for shipment redirection. For example,shipments/items containing various item types (e.g., predetermined itemtypes, such as chemicals, explosives, firearms, alcohol, tobacco, drugs,and/or the like) may be ineligible for shipment redirection, andaccordingly the central computing entity 110 may be configured to updatethe PLD information/data corresponding to such shipments/items toindicate that the shipments/items are not eligible for shipmentredirection.

In certain embodiments, upon determining that the request to redirectthe shipment/item is possible (e.g., based on a determination that therequest to redirect the shipment/item satisfies applicable criteria),the central computing entity 110 may be configured to determine anappropriate methodology for effecting the requested redirection (and/orother location-specific service) (e.g., based on the current location ofthe delivery vehicle as determined based on received locationinformation/data and/or the current time). For example, the centralcomputing entity 110 may be configured to determine whether the lastmile delivery vehicle 100 containing the shipment/item is able todeliver the shipment/item to the alternative intended destination 704without a significant deviation from the assigned delivery route,whether another delivery vehicle 100 (e.g., a service provider) mayeffect delivery to the alternative intended destination 704 within apredefined period of time, whether the shipment/item should beredirected back to the sort location associated with the deliveryvehicle 100 and transported to a second sort location to effect deliveryto the alternative intended destination, and/or the like.

As shown at Block 603 of FIG. 6, the central computing entity 110 may beconfigured to determine whether delivery to the alternative intendeddestination 704 may be effected by the last mile delivery vehicle 100traversing the assigned delivery route without a substantial deviationfrom the assigned delivery route. In various embodiments, adetermination of whether the last mile delivery vehicle 100 may effectdelivery to the alternative intended destination 704 may be impacted bythe current location of the delivery vehicle 100 along the assigneddelivery route and the location of the remaining (e.g., untraversed)portion of the assigned delivery route relative to the location of thealternative intended destination 704. For example, the central computingentity 110 may be configured to determine that the delivery vehicle 100containing the shipment/item is eligible to effect delivery of theshipment/item to the alternative intended destination 704 upon adetermination that the delivery vehicle 100 may visit the alternativeintended destination 704 (e.g., in addition to or in lieu of visitingthe initial intended destination 703) without significantly modifyingthe assigned delivery route for the vehicle 100. The central computingentity 110 may be configured to determine that the delivery vehicle 100may visit the alternative intended destination 704 without significantlymodifying the assigned delivery route for the vehicle 100 upondetermining that a modified version of the remaining (e.g., untraversed)portion of the delivery route that incorporates a stop at thealternative intended destination 704 satisfies applicable criteriastored within the central computing entity 110. For example, the centralcomputing entity 110 may be configured to determine that the modifiedversion of the remaining portion of the delivery route satisfiesapplicable criteria upon a determination that the length of the modifiedversion of the remaining portion of the delivery route is within apredefined length of the length of the unmodified (e.g., original)version of the remaining portion of the delivery route. As a specificexample, the central computing entity 110 may be configured to determinethat a modified version of the remaining portion of the delivery routeis not significantly different from the unmodified portion of thedelivery route upon a determination that the modified version of theremaining portion of the delivery route is less than 5 miles greaterthan the unmodified version of the remaining portion of the deliveryroute. As yet other non-limiting embodiments, the predefined criteriafor determining whether the modified version of the remaining portion ofthe delivery route is significantly different than the unmodifiedversion of the remaining portion of the delivery route may be based onan estimated time difference between the modified and unmodifiedversions of the remaining portion of the delivery route (e.g., within a15 minute difference), based on an estimated amount of fuel to beutilized (e.g., within ⅛ of a gallon of estimated fuel usage differencebetween the modified and unmodified versions of the remaining portion ofthe delivery route), and/or the like.

As indicated at Block 612 of FIG. 6, upon determining that the last miledelivery vehicle 100 can effect delivery of the shipment/item to thealternative intended destination 704, the central computing entity 110may be configured to facilitate delivery of the shipment/item to thealternative intended destination 704 by the last mile delivery vehicle100. In various embodiments, the central computing entity 110 may beconfigured to generate one or more flags within the PLD information/datafor the shipment/item to indicate that the shipment/item is redirectedto the alternative destination location 704, to update the assigneddelivery route for the last mile delivery vehicle 100, to transmit anotification to the vehicle 100 and/or a mobile computing entity 105associated with a vehicle operator, and/or the like.

With reference again to FIG. 6, upon determining that the alternativeintended destination 704 is not along the remaining portion of thedelivery route assigned to the last mile delivery vehicle 100, thecentral computing entity 110 may be configured to determine whether theshipment/item may be delivered to the alternative destination location704 within a predefined time period and/or whether the alternativeintended destination is within a predefined geographic area (e.g.,within a predefined distance from the initial intended destination 703,within a predefined distance from the delivery route, and/or the like),such that a service provider 100 a may deliver the shipment/item fromthe last mile delivery vehicle 100 to the alternative intendeddestination 704, as indicated at Block 604.

In various embodiments, the central computing entity 110 may beconfigured to determine whether the shipment/item is eligible fordelivery to the alternative intended destination 704 via a serviceprovider 100 a based on one or more criteria, such as one or moretime-based criteria and/or one or more location-based criteria. Forexample, the central computing entity 110 may be configured to determinewhether delivery may be made from the last mile delivery vehicle 100 tothe alternative intended destination 704 within a predefined amount oftime (e.g., 2 hours), prior to a predefined deadline (e.g., 7 PM),and/or the like. Accordingly, upon determining that delivery to thealternative intended destination 704 may not be effected by the lastmile delivery vehicle 100 as discussed herein, the central computingentity 110 may be configured to determine an estimated time to effectdelivery of the shipment/item to the alternative intended destination704 and/or an estimated delivery time for the shipment/item at thealternative intended destination 704 if delivered by a service provider100 a. In various embodiments, the central computing entity 110 may beconfigured to query one or more databases and/or externalinformation/data sources (e.g., third party databases) to determine anestimated delivery time for the shipment/item by a service provider 100a. For example, the central computing entity 110 may be configured toquery a map database, a traffic database, a third party vehicle providerdatabase, and/or the like to determine whether delivery may be madeaccording to the one or more of the time-based criteria.

In various embodiments, the central computing entity 110 may beconfigured to determine whether the alternative intended destination 704satisfies one or more location-based criteria. For example, the centralcomputing entity 110 may be configured to compare the location of thealternative intended destination 704 against the location of the initialintended destination 703, the location of the assigned delivery routefor the last mile delivery vehicle 100 carrying the shipment/item, thelocation of a predefined geographical area, and/or the like. In variousembodiments, the central computing entity 110 may be configured todetermine that the shipment/item is eligible for delivery via a serviceprovider 100 a to the identified alternative intended destination 703upon a determination that the alternative intended destination 704satisfies the location-based criteria. As non-limiting examples, thecentral computing entity 110 may be configured to determine that thealternative intended destination 704 satisfies the location-basedcriteria upon a determination that the alternative intended destination704 is within a predefined distance of the initial intended destination703, upon a determination that the alternative intended destination iswithin a predefined distance of the assigned delivery route (e.g., thealternative intended destination is within a predefined distance of theclosest point of the assigned delivery route), upon a determination thatthe alternative intended destination 704 is within a predefinedgeographical area (e.g., the same city as the initial intendeddestination 703, the same postal area (e.g., zip code) as the initialintended destination, the same county as the initial intendeddestination, and/or the like), and/or the like.

In various embodiments, various shipments/items may be identified asineligible for delivery via a service provider 100 a based on one ormore shipment/item-based criteria. For example, a shipper and/orintended recipient may provide information/data to the central computingentity 110 (e.g., via one or more user computing entities) indicatingthat one or more shipments/items are ineligible for delivery via aservice provider 100 a. In other embodiments, the central computingentity 110 may compare the PLD information/data corresponding to aparticular shipment/item against one or more criteria to determinewhether the shipment/item is eligible for delivery via a serviceprovider 100 a. For example, shipments/items containing certain itemtypes (e.g., chemicals, explosives, firearms, drugs, and/or the like)may be identified as ineligible for delivery via a service provider 100a. As yet other examples, the central computing entity 110 may beconfigured to determine whether the size and/or weight of theshipment/item satisfies applicable criteria to enable delivery via aservice provider 100 a. For example, the central computing entity 110may be configured to compare the PLD information/data of theshipment/item against a maximum weight and/or maximum size threshold todetermine whether the shipment/item is eligible for delivery via aservice provider 100 a. In embodiments in which the central computingentity 110 determines that delivery via a service provider 100 a isunavailable for a particular shipment/item, the central computing entity110 may be configured to reroute the shipment/item back to the sortlocation such that the shipment/item may be placed onto an appropriatelast mile delivery vehicle 100 for delivery to the alternative intendeddestination 704 upon receipt of a request to redirect the shipment/itemto the alternative intended destination.

With reference to Block 613 of FIG. 6, upon a determination that thealternative intended destination 704 does not satisfy the one or morecriteria for delivery of the shipment/item to the alternative intendeddestination 704 via a service provider 100 a, the central computingentity 110 may be configured to facilitate redirection of theshipment/item to an appropriate last mile delivery vehicle 100 to effectdelivery to the alternative intended destination 704. Accordingly, thecentral computing entity 110 may update the PLD information/datacorresponding to the shipment/item to indicate the alternative indicateddestination 704, to generate a notification to be transmitted to thedelivery vehicle 100 and/or a mobile device associated with the vehicleoperator to refrain from delivering the shipment/item at the initialintended destination 703 and to return the shipment/item to the sortlocation such that the shipment/item may be rerouted to the appropriatesort location and/or delivery vehicle 100 to effect delivery to thealternative intended destination.

Upon determining that the shipment/item may be delivered to thealternative intended destination 704 via a service provider 100 a, thecentral computing entity 110 may be configured to arrange delivery via aservice provider 100 a, as discussed herein.

2. Arranging Delivery Via a Service Provider

In various embodiments, the service provider 100 a may be a seconddelivery vehicle (e.g., owned and/or operated by the carrier), a thirdparty vehicle (e.g., a privately owned vehicle owned and/or operated byan individual; a vehicle owned and operated by a third party serviceprovider, and/or the like), and/or the like. In various embodiments, theservice provider 100 a may be one of a plurality of service providersoperating and/or managed by a peer-based entity (e.g., Uber, UberEats,Lyft, GetMe, and/or the like) configured to manage, arrange, and/orotherwise distribute tasks among a plurality of individuals viaelectronic communication with mobile devices associated with each of theplurality of individuals. In various embodiments, the peer-based entitymay be configured to arrange rides for individuals in one morepeer-based service providers 100 a, shipping services (e.g.,shipment/item deliveries), local courier services (e.g., food deliveryand/or pick-up), and/or the like. In various embodiments, the centralcomputing entity 110 may be configured to select an appropriate serviceprovider 100 a from a plurality of service providers 100 a.

Upon determining that a shipment/item is eligible for delivery to thealternative intended destination 704 (and/or another requestedlocation-specific service) via a service provider 100 a (as indicated atBlock 604), the central computing entity 110 may be configured toidentify one or more service providers 100 a available for delivery ofthe shipment/item. In various embodiments, each of a plurality ofservice providers 100 a may have a corresponding service providerprofile (e.g., stored within the central computing entity 110 and/or athird party computing entity). The service provider profile may compriseinformation/data indicative of a vehicle type (e.g., sedan, coupe, SUV,crossover, open-bed truck, closed cargo truck, cargo van, minivan,and/or the like), a volume of cargo space available for placement of ashipment/item within the vehicle (e.g., identified as a maximumshipment/item size and/or a cargo area volume), a maximum shipment/itemweight that may be transported by the vehicle, one or more licensesassociated with an operator of the service provider 100 a (e.g.,hazardous material transport license, commercial vehicle license, and/orthe like), and/or the like. Upon determining that the shipment/item maybe delivered by a service provider 100 a, the central computing entity110 may be configured to compare the PLD information/data correspondingto the shipment/item against one or more service provider profiles toidentify one or more service providers 100 a capable of transporting theshipment/item. For example, the central computing entity 110 may beconfigured to compare known dimensions of the shipment/item againstknown cargo dimensions of vehicles as stored in the service providerprofiles 100 a. Moreover, the central computing entity 110 may beconfigured to identify one or more service providers 100 a that areworking (on-duty, available, and/or other words used hereininterchangeably) such that only those vehicles that are operating andoffering transportation services may be considered. The centralcomputing entity 110 may thus filter the plurality of service providers100 a such that the central computing entity 110 only considers serviceproviders 100 a that satisfy one or more applicable criteria as beingeligible to transport the shipment/item to the alternative destinationwhen searching for an eligible service provider 100 a.

In certain embodiments, the central computing entity 110 may beconfigured to identify one or more service providers 100 a satisfyingone or more location-based criteria. For example, the central computingentity 110 may be configured to receive service provider locationinformation/data from each of a plurality of service providers 100 a(e.g., available service providers 100 a) indicative of a currentlocation of each of the service providers 100 a. As discussed herein,the service provider location data may be generated by a locationdetermining aspect in association with a service provider computingentity carried by the service provider 100 a. The central computingentity 110 may be configured to compare the service provider locationinformation/data against location-based criteria, such as a maximumdistance away from the delivery route, a predefined area (e.g., ageofenced area) within which the service provider 100 a should belocated, and/or the like, to determine whether the service provider 100a is eligible to deliver the shipment/item to the alternativedestination location. In various embodiments, the central computingentity 110 may be configured to filter the one or more service providers100 a such that only those service providers 100 a satisfying thelocation-based criteria are considered for delivering the shipment/itemto the alternative destination location.

Upon filtering the one or more service providers 100 a (e.g., based ontime-based criteria, shipment/item based criteria, location-basedcriteria, and/or the like), the central computing entity 110 may beconfigured to apply one or more selection criteria to select a singleservice provider 100 a to effect delivery of the shipment/item to thealternative intended destination. For example, the central computingentity 110 may be configured to select the closest service provider 100a to the last mile delivery vehicle 100 (e.g., based on locationinformation/data associated with the delivery vehicle 100 and/or theservice provider 100 a), the service provider 100 a offering the lowestcost to deliver the shipment/item to the alternative intendeddestination, the service provider 100 a satisfying shipper and/orintended recipient preferences, the service provider 100 a having thehighest customer ranking, and/or the like. As a specific example, thecentral computing entity 110 may be configured to receive (e.g., in realtime) service provider location information/data from each of aplurality of service providers 100 a. The central computing entity 110may be configured to compare the current location of each serviceprovider 100 a (e.g., as determined by most recent service providerlocation information/data for each of the plurality of service providers100 a) against route information/data and/or delivery vehicle locationinformation/data for the delivery vehicle 100 (e.g., as determined bymost recent location information/data received from the delivery vehicle100) to identify a service provider 100 a closest to the deliveryvehicle 100 and/or the delivery route assigned to the delivery vehicle100.

As another example, the central computing entity 110 may be configuredto identify one or more service providers 100 a that may meet thedelivery vehicle 100 at one or more potential handoff locations alongthe delivery route (e.g., at an estimated time that the delivery vehicle100 would arrive at each of the potential handoff locations as thedelivery vehicle 100 traverses the assigned route). Accordingly, aplurality of service providers 100 a may be determined eligible fortransporting the shipment/item to the alternative intended destinationupon determining that a plurality of service providers 100 a may becapable of meeting the delivery vehicle 100 at one or more handofflocations. In such embodiments, one or more additional criteria (e.g.,cost, time-based criteria, random selection, and/or the like) may beutilized to select one of the service providers 100 a to transport theshipment/item.

In certain embodiments, the central computing entity 110 may beconfigured to select a service provider 100 a based on a plurality ofcriteria. For example, the central computing entity 110 may beconfigured to assign a weight to each considered criteria and togenerate an overall score based at least in part on the determinedweighted criteria. The central computing entity 110 may be configured toselect the service provider 100 a having the highest (or lowest)weighted score. As just one non-limiting example, the central computingentity 110 may be configured to consider a plurality of: the distancebetween the service provider 100 a and the delivery vehicle 100, therating of the service provider 100, the cost (e.g., estimated cost) todeliver the shipment/item to the alternative intended destination by theservice provider 100 a, and/or the like when selecting a particularservice provider 100 a to deliver the shipment/item to the alternativeintended destination. In certain embodiments, the central computingentity 110 may be configured to generate a ranked list of possibleservice providers 100 a that are determined to be eligible fortransporting the shipment/item to the alternative intended destination.In such embodiments, the central computing entity 110 may be configuredto select the highest ranked available service provider 100 a totransport the shipment/item to the alternative intended destination.

Although discussed herein as the central computing entity 110 selectinga particular service provider 100 a to effect delivery of theshipment/item to the alternative intended destination, it should beunderstood that, in various embodiments, the central computing entity110 may be configured to query a third party computing entity (e.g., apeer-based service provider management system) to select a serviceprovider 100 a. For example, the central computing entity 110 may beconfigured to transmit a request to reserve and/or engage a serviceprovider 100 a to the third party computing entity, which then selectsand provides a service provider 100 a to transport the shipment/item tothe alternative intended destination 704. As discussed herein, therequest may identify the alternative intended destination 704 and mayidentify one or more potential handoff locations where the serviceprovider 100 a can meet the last mile delivery vehicle 100 to obtain thepackage and/or one or more potential handoff times. Upon receipt of therequest, the third party computing entity may select a service provider100 a, a handoff location 705, and/or a handoff time to effecttransportation of the shipment/item from the last mile delivery vehicle100 to the alternative intended destination.

With reference again to FIG. 6, the central computing entity 110 mayidentify a handoff location 705 and/or time at which the serviceprovider 100 a meets the last mile delivery vehicle 100 to effect ahandoff of the shipment/item from the last mile delivery vehicle 100 tothe service provider 100 a, as shown at Block 606. Although illustratedin separate representative Blocks in FIG. 6, the steps for identifying aservice provider 100 a and for identifying a handoff time and location705 may occur simultaneously. In various embodiments, the selection of aparticular service provider 100 a may impact a selection of a handofftime and/or handoff location 705, and/or vice versa. For example, afirst service provider 100 a may be proximate a first potential handofflocation 705 at a first time, and a second service provider 100 a may beproximate a second potential handoff location at a second time. Uponselecting the second service provider 100 a to effect transportation ofthe shipment/item, the central computing entity 110 may determine thatthe shipment/item handoff should occur at the second handoff time andlocation.

In various embodiments, the one or more potential handoff locations maybe particular locations along the assigned route of the last miledelivery vehicle 100. In certain embodiments, the one or more potentialhandoff locations may be preassigned stops (e.g., delivery stops and/orpickup stops for other shipments/items) where a service provider 100 acould meet the last mile delivery vehicle 100 to effect the transfer ofthe shipment/item from the delivery vehicle 100 to the service provider100 a. In yet other embodiments, the one or more potential handofflocations may be identified as potential locations where the last miledelivery vehicle 100 could park and which would not require asignificant deviation from the preassigned delivery route of the vehicle100 (identified in accordance with the discussion regarding significantdeviations from the delivery route provided above). The one or morepotential handoff times may be identified based at least in part on theone or more potential handoff locations. The one or more potentialhandoff times may be identified as the estimated times at which the lastmile delivery vehicle 100 is expected to reach the one or more potentialhandoff locations. Accordingly, in certain embodiments, each potentialhandoff location may have a corresponding potential handoff time. Invarious embodiments, identifying a handoff location 705 may comprisecomparing route information/data indicative of the assigned route forthe delivery vehicle 100 against delivery vehicle locationinformation/data indicative of a current location of the deliveryvehicle along the assigned route, in order to identify an untraversedportion of the assigned route. Upon identifying the untraversed portionof the assigned route, the central computing entity 110 may beconfigured to identify one or more potential handoff locations (andcorresponding potential handoff times) along the assigned route. Forexample, a plurality of potential handoff locations may be stored inassociation with the central computing entity 110, such that the centralcomputing entity 110 may be configured to select one or more of thepotential handoff locations located along the assigned route, and todetermine an estimated time at which the delivery vehicle will arrive atthe selected one or more potential handoff locations in order toidentify corresponding handoff times. As yet another non-limitingexample, the central computing entity 110 may be configured to monitorthe untraversed portion of the assigned route, and to identify one ormore potential handoff locations that satisfy stored handoff locationcriteria. For example, the handoff location criteria may identifyparking areas within a predefined distance of the untraversed portion ofthe assigned route, preassigned vehicle stops, and/or the like aspotential handoff locations.

As noted above, the central computing entity 110 may be configured toidentify a service provider 100 a, a handoff location 705, and/or ahandoff time to enable the service provider 100 a to deliver theshipment/item at the alternative intended destination 704. However, itshould be understood that the central computing entity 110 may beconfigured to transmit a request for a service provider 100 a to a thirdparty computing entity (e.g., a peer based vehicle and/or serviceprovider provider) to select a service provider 100 a based at least inpart on characteristics of the shipment/item, the location of thealternative intended destination, the location of one or more potentialhandoff locations and times, and/or the like. In such embodiments, thethird party computing entity may transmit information/data identifyingthe selected service provider 100 a to the central computing entity 110.

3. Delivery from the Last Mile Delivery Vehicle to the AlternativeIntended

Destination

Upon selecting a service provider 100 a, a handoff time, and a handofflocation 705, the last mile delivery vehicle 100 and the serviceprovider 100 a (and their respective operators) may meet at the handofflocation 705 at the handoff time to transfer the shipment/item from thedelivery vehicle 100 to the service provider 100 a. As indicated atBlock 607, in various embodiments, the carrier (and/or the centralcomputing entity 110) may request verification of the identity of theservice provider 100 a (and the associated service provider operator)prior to transferring possession of the shipment/item to the serviceprovider 100 a. In various embodiments, the central computing entity 110may transmit identity verification information/data identifying theservice provider 100 a to the last mile delivery vehicle 100 and/or amobile computing entity 105 associated with the vehicle operator. Invarious embodiments, the identity verification information/data maycomprise a vehicle identifier, a name of the service provider, a photoof the service provider and/or the service provider vehicle, and/or thelike. In certain embodiments, verification of the identity of theservice provider 100 a may comprise visual verification of the identityof the service provider 100 a by the last mile delivery vehicleoperator. In such embodiments, the delivery vehicle operator may provideuser input to the mobile device 105 and/or the delivery vehicle 100indicating that the delivery vehicle operator verified the identity ofthe service provider 100 a.

In various embodiments, the identity verification process may utilizeelectronic identity verification procedures to verify the identity ofthe service provider at the handoff location. For example, the centralcomputing entity 110 may transmit (e.g., directly and/or via one or morethird party computing entiies) a verification code (e.g., a barcode, aQR code, a Maxicode, an alphanumeric string, a symbol, and/or the like)to one or more of the delivery vehicle 100, a mobile device 105associated with the delivery vehicle operator, and/or a mobile device105 associated with the service provider. To verify the identity of theservice provider 100 a, the verification code may be input (e.g., viauser input, via scanning, via NFC data transmission, via Bluetooth datatransmission, and/or the like) into another of the delivery vehicle 100,a mobile device 105 associated with the delivery vehicle operator,and/or a mobile device 105 associated with the service provider, and theverification code may be transmitted (e.g., directly and/or via one ormore third party computing entities) to the central computing entity110. Upon receipt, the central computing entity 110 may compare theverification code and information/data identifying the source of thetransmitted verification code against stored information/dataidentifying an expected verification code and an expected source of theverification code to verify the identity of the service provider 100 a.Upon identifying a match between the received verification code andsource of the verification code and the expected verification code andexpected source of the verification code, the central computing entity110 may verify the identity of the service provider 100 a. In variousembodiments, the central computing entity 110 may be configured totransmit (e.g., directly and/or via one or more third party computingentities) a notification to one or more of the delivery vehicle 100, amobile device 105 associated with the delivery vehicle operator, and/ora mobile device 105 associated with the service provider to inform thedelivery vehicle operator and/or the service provider that the identityof the service provider has been verified.

As yet another example, two or more of the delivery vehicle 100, themobile device 105 associated with the delivery vehicle operator, and/orthe mobile device 105 associated with the service provider may beconfigured to perform a virtual handshake to verify the identity of theservice provider 100 a. In such embodiments, the central computingentity 110 may be configured to transmit (e.g., directly and/or via oneor more third party computing entities) virtual handshakeinformation/data signals to two or more of the delivery vehicle 100, amobile device 105 associated with the delivery vehicle operator, and/ora mobile device 105 associated with the service provider. While at thehandoff location and time, two or more of the delivery vehicle 100, amobile device 105 associated with the delivery vehicle operator, and/ora mobile device 105 associated with the service provider may perform thevirtual handoff, for example, via wireless communications between thetwo or more of the delivery vehicle 100, a mobile device 105 associatedwith the delivery vehicle operator, and/or a mobile device 105associated with the service provider (e.g., NFC communications,Bluetooth communications, and/or the like). Upon performing the virtualhandshake, one or more of the delivery vehicle 100, a mobile device 105associated with the delivery vehicle operator, and/or a mobile device105 associated with the service provider may transmit a signal to thecentral computing entity (e.g., directly and/or via a third partycomputing entity) indicating the virtual handshake has been performed toverify the identity of the service provider 100 a.

As indicated at Block 608 of FIG. 6, the shipment/item is transferredfrom the last mile delivery vehicle 100 to the service provider 100 a.In various embodiments, the transfer may occur after verification of theidentity of the service provider 100 a, however in certain embodiments,the shipment/item may be transferred without verification of the serviceprovider 100 a. In various embodiments, upon transferring theshipment/item to the service provider 100 a, one or more of the deliveryvehicle 100, a mobile device 105 associated with the delivery vehicleoperator, and/or a mobile device 105 associated with the serviceprovider may transmit a signal to the central computing entity 110indicating that the shipment/item has been transferred to the serviceprovider 100 a. Upon receipt, the central computing entity 110 mayupdate the PLD information/data to reflect the transfer, and mayfacilitate tracking of the service provider location as a proxy for thelocation of the shipment/item as it is carried to the alternativeintended destination 704, as indicated at Block 609 of FIG. 6.

As discussed herein, the service provider computing entity may beconfigured to continuously and/or periodically transmit information/dataindicative of the location of the service provider computing entity tothe central computing entity 110 while the service provider istransporting the shipment/item. In various embodiments, the centralcomputing entity 110 may update the PLD information/data correspondingto the shipment/item to reflect the updated location of theshipment/item (based on the location of the service provider computingentity).

Moreover, as discussed above, the service provider computing entity maybe configured to generate delivery verification information/data toreflect delivery of the shipment/item at the alternative intendeddestination 704, as indicated at Block 610. For example, the serviceprovider computing entity may be configured to generate imageinformation/data showing the shipment/item at the alternative intendeddestination, showing at least a portion of the alternative intendeddestination 704 (e.g., a house number corresponding to the alternativeintended destination), a signature of the intended recipient, and/or thelike. As yet other embodiments, the service provider computing entitymay be configured to accept a delivery verification code (e.g., analphanumeric code, a barcode, a QR code, a Maxicode, and/or the like)placed at the alternative intended destination, and/or the like. Invarious embodiments, the delivery verification information/data maycomprise identity verification information/data for a shipment/itemrecipient. In various embodiments, the identity verificationinformation/data for the shipment/item recipient may comprise asignature of the shipment/item recipient (e.g., captured via user inputon the service provider computing entity), a photo of the shipment/itemrecipient, a photo of the shipment/item recipient's ID (e.g., passport,driver's license, and/or the like), and/or the like. In variousembodiments, the identity verification information/data for the packagerecipient may be similar to that described above for verifying theidentity of the service provider at the time the shipment/item ishanded-over to the service provider. Accordingly, the identityverification process for a shipment/item recipient may compriseelectronic identity verification procedures (e.g., receiving identityverification information/data from a central computing entity 110,comparing identity verification data received by a mobile computingentity 105 owned by the shipment/item recipient against identityverification data received by the service provider computing entity,and/or the like).

In various embodiments, the service provider computing entity may beconfigured to transmit the delivery verification information/data to thecentral computing entity 110. The central computing entity 110 may beconfigured to update the PLD information/data corresponding to thedelivered shipment/item to include the delivery verificationinformation/data and/or to include information/data indicating that theshipment/item was delivered to the alternative intended destination 704.

Moreover, in various embodiments, the service provider computing entitymay be configured to receive payment from the shipment/item recipientfor additional costs/fees associated with the delivery redirection.Accordingly, the service provider computing entity may utilize one ormore payment processing components (e.g., card readers, NFC readers,and/or the like) to receive payment from the shipment/item recipient atthe time of delivery. In such embodiments, the service providercomputing entity may be configured to receive information/data from thecentral computing entity 110 indicative of an amount owed by theshipment/item recipient (e.g., via a computer program enablingcommunication between the central computing entity 110 and the serviceprovider computing entity). Moreover, the service provider computingentity may be configured to receive payment information/data (e.g., viathe payment processing component) to settle the amount owed by theshipment/item recipient. The service provider computing entity may beconfigured to process the payment locally (e.g., via communications withone or more banking institutions), and/or the service provider computingentity may be configured to transmit payment processing information/datato the central computing entity 110 for processing. In variousembodiments, the service provider computing entity may be configured toencrypt at least a portion of the payment information before processingand/or before transmitting the same to the central computing entity 110.

In various embodiments, the central computing entity 110 may facilitatepayment of the service provider 100 a for completing the delivery uponreceipt of the delivery verification information/data. In embodiments inwhich the service providers 100 a are independent contractors,peer-based service providers, and/or the like, the carrier may providepayment to the service providers 100 a for completing deliveries ofshipments/items to respective alternative destination locations 704.Accordingly, upon receipt of delivery verification information/data, thecentral computing entity 110 may initiate payment to the serviceprovider 100 a, as indicated at Block 611. For example, the centralcomputing entity 110 may transmit a signal to a payment processingentity to transfer funds to the service provider 100 a (e.g., apre-established account associated with the service provider). Incertain embodiments, the central computing entity 110 may wait for apredetermined escrow period (e.g., hours, days, weeks, and/or the like)prior to transferring funds to the service provider. For example, thecentral computing entity 110 may be configured to wait a period of timeto enable an intended recipient to complain that a shipment/item was notproperly delivered before transferring funds. As yet another example,the central computing entity 110 may be configured to enable fundstransfers to service provider accounts periodically (e.g., weekly,bi-weekly, monthly, and/or the like).

c. Shipment/Item Pick-up via Service Providers

In various embodiments, service providers may be utilized to performshipment/item pick-ups from a shipment/item source. For example, theservice providers may pick-up shipments/items to be returned to ashipment/item origin (e.g., shipments/items originally shipped to arecipient, and for which the recipient wishes to return theshipment/item to the original shipper). In such embodiments, the serviceproviders may pick-up shipments/items from one or more shipment origins(e.g., shipper residences, shipper businesses, and/or the like) andtransport the shipments/items to a delivery vehicle at a determinedhand-off location and hand-off time.

The process for receiving a pick-up request, selecting a serviceprovider, and selecting a hand-off location and a hand-off time may beanalogous to that discussed herein in reference to processes forreceiving a delivery redirection request for a shipment/item already ona delivery vehicle for delivery to an initial intended destinationlocation; selecting a service provider to transport the shipment/itemfrom the delivery vehicle to the alternative intended destinationlocation; and selecting a hand-off location and a hand-off time tocomplete the transfer from the delivery vehicle to the service provider.

As an example, the central computing entity 110 may receive a pick-uprequest from a shipment/item shipper (e.g., via a graphical userinterface available via a shipper's computing entity). In variousembodiments, the pick-up request may comprise shipment/iteminformation/data, such as information/data indicative of the size,weight, content, and/or the like of the shipment/item to be picked-up,the requested pick-up location, and/or the like. Upon receipt of thepick-up request, the central computing entity 110 may be configured todetermine whether the shipment/item should be picked up by a deliveryvehicle or a service provider that can transport the shipment/item to adelivery vehicle. For example, the central computing entity 110 may beconfigured to compare the requested pick-up location against the currentlocation of one or more delivery vehicles, to determine whether thepick-up location is along an untraversed portion of a route assigned toone or more delivery vehicles.

Upon determining that the requested pick-up location is along anuntraversed portion of a route assigned to a particular deliveryvehicle, the central computing entity 110 may assign a pick-up stop to adelivery vehicle corresponding to the pick-up request. The pick-up stopmay be incorporated into the route assigned to the delivery vehicle(e.g., by transmitting updated route data to the delivery vehicle and/ora mobile computing entity 105 associated with the delivery vehicle),such that the delivery vehicle is scheduled to stop at the pick-uplocation along the route.

Upon determining that the requested pick-up location is not along anuntraversed portion of a route assigned to a delivery vehicle, and/orupon determining that a delivery vehicle is otherwise unavailable topick-up the shipment/item, the central computing entity 110 may beconfigured to request pick-up services from one or more serviceproviders, as discussed herein in reference to requesting deliveryservices. The central computing entity 110 may utilize one or morealgorithms to select an appropriate service provider to complete thepick-up (e.g., based on the current locations of the one or more serviceproviders, the carrying capacity of one or more service providers, arating associated with one or more service providers, and/or the like).

As discussed herein in reference to features for assigning a deliverytask to a particular service provider, the central computing entity 110may be configured to transmit information/data to the service providerindicative of the location of the pick-up location. The centralcomputing entity 110 may additionally be configured to identity ahand-off location and a hand-off time at which the service providerhands the shipment/item over to a delivery vehicle. For example, asdiscussed above in reference to selecting a hand-off location andhand-off time for a delivery service, the central computing entity 110may identity an appropriate hand-off location and hand-off time based onthe current location of the service provider, the pick-up location, theestimated amount of time for the service provider to reach the pick-uplocation and to travel to one or more potential hand-off locations, thecurrent location of the delivery vehicle, and/or the like.

In various embodiments, while identifying a hand-off location and ahand-off time for the shipment/item to be provided to a deliveryvehicle, the central computing entity 110 may be configured to identifyan appropriate delivery vehicle to receive the shipment/item from theservice provider. Accordingly, the central computing entity 110 may beconfigured to select a delivery vehicle from a plurality of deliveryvehicles that is scheduled to arrive at a hand-off location at about thehand-off time. Accordingly, the central computing entity 110 may beconfigured to identify a plurality of hand-off locations for the serviceprovider, as well as an estimated time at which the service provider islikely to be able to arrive at the potential hand-off locations.Similarly, the central computing entity 110 may be configured toidentify a plurality of potential hand-off locations and correspondingarrival times for a plurality of delivery vehicles.

The central computing entity 110 may then compare the potential hand-offlocations and corresponding arrival times for the service provider withthe potential hand-off locations and corresponding arrival times for theplurality of delivery vehicles, and may select a hand-off location andcorresponding arrival time that overlaps between the service providerand one of the delivery vehicles. In various embodiments, the centralcomputing entity 110 may comprise one or more criteria for selecting aparticular hand-off location and hand-off time when a plurality ofhand-off locations and corresponding arrival times overlap between theservice provider and one or more delivery vehicles. As just onenon-limiting example, the central computing entity 110 may be configuredto select the hand-off location and corresponding hand-off time locatedclosest to the pick-up location for the shipment/item.

Upon selecting a service provider, a hand-off location and a hand-offtime, the central computing entity 110 may be configured to transmitpick-up instructions to the service provider computing entity, and/or toupdate the delivery route assigned to the delivery vehicle identified asthe receiving delivery vehicle to incorporate the hand-off location as astop along an untraversed portion of the route.

As discussed herein in reference to the delivery redirection process,the central computing entity 110 may be configured to track the locationof the service provider as the service provider completes the pick-upprocess. In various embodiments, the service provider computing entitymay be configured to collect pick-up verification data (e.g., similar todelivery verification data) while at the pick-up location. For example,the pick-up verification data may comprise one or more images collectedby the service provider computing entity while at the pick-up location(e.g., images of the shipment/item; images of the pick-up location;images of the shipment/item shipper; images of the shipment/itemshipper's ID; and/or the like).

Moreover, in various embodiments, the service provider computing entitymay be configured to process a payment from the shipment/item shipperwhile at the pick-up location. Like the process discussed herein inreference to delivery processes, the service provider computing entitymay be configured to receive data from the central computing entity 110indicative of an amount owed by the shipment/item shipper. The serviceprovider computing entity may then receive payment information/data,such as via a payment processing component, and may enable processing ofthe payment information/data locally and/or after transfer of the sameto the central computing entity 110.

After picking-up the shipment/item from the pick-up location, theservice provider may transport the shipment/item to the identifiedhand-off location by the identified hand-off time. While at the hand-offlocation, the service provider may provide the shipment/item to thedelivery vehicle (e.g., personnel operating the delivery vehicle).Moreover, in certain embodiments, an identity verification process maybe performed between the delivery vehicle (and/or a mobile computingentity 105 associated with the delivery vehicle) and the serviceprovider and/or the service provider computing entity. Like theidentification verification process described herein when ashipment/item is provided to a service provider for final delivery to analternative intended destination location, the identity verificationprocess performed when a shipment/item is provided to a delivery vehiclemay comprise one or more electronic and/or manual identity verificationprocedures (e.g., by comparing identity verification data received bythe mobile computing entity 105 associated with the delivery vehicle andidentity verification data received by the service provider computingentity; by performing a visual comparison between the service providerand a known photo of the service provider; and/or the like).

Moreover, at the hand-off location, the delivery vehicle (and/orpersonnel associated with the delivery vehicle) may scan theshipment/item to generate information/data indicating that theshipment/item has been received at the delivery vehicle. The generateddata may be transmitted to the central computing entity 110 to verifythat the shipment/item is successfully transferred to the deliveryvehicle. In various embodiments, upon receiving data indicating that theshipment/item is successfully transferred to the delivery vehicle, thecentral computing entity 110 may be configured to process a payment tothe service provider for services rendered in transporting theshipment/item from the pick-up location to the delivery vehicle. Asdiscussed above in reference to payment processing for deliveryservices, the central computing entity 110 may be configured to processpayment to the service provider after a predefined time period, and/orthe like.

CONCLUSION

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

In various embodiments, various delivery redirection methodologies maybe utilized at various points during a delivery process. Although theforegoing description provides a discussion of various deliveryredirection methodologies as being available at corresponding pointsduring a delivery process for a shipment/item, it should be understoodthat alternative delivery redirection processes may be utilized. Forexample, if a delivery redirection request is received before ashipment/item is out for delivery on an initial delivery vehicle, thedelivery redirection process may utilize a service provider to transportthe shipment/item from the initial delivery vehicle to the alternativeintended destination location once the shipment/item has been loadedonto the delivery vehicle. As yet another example, a deliveryredirection process for a shipment/item already out for delivery on adelivery vehicle may be redirected by returning the shipment/item to ahub, and redirecting the shipment/item onto a second delivery vehiclefrom the hub, regardless of the relative proximity between the initialintended destination location and the alternative intended destinationlocation.

What is claimed is:
 1. A method for engaging a service provider toperform a location-specific service involving an item, the methodcomprising steps for: receiving a request to deliver an item located ona delivery vehicle traversing an assigned vehicle route to analternative destination, wherein an initial destination for the item ison the assigned vehicle route; in response to determining thatadditional fuel the delivery vehicle would expend by altering theassigned vehicle route to deliver the item to the alternativedestination is greater than a threshold amount of fuel, initiating aplan to handoff the item to a service provider for delivery to thealternative destination; monitoring, based at least in part on locationdata received from the delivery vehicle, a location of the deliveryvehicle; monitoring a location of one or more service providers;identifying one or more potential meet locations and correspondingpotential meet times; comparing the location of one or more serviceproviders against the one or more potential meet locations andcorresponding meet times to identify one or more eligible serviceproviders, wherein the one or more eligible service providers areidentified as capable of traveling to at least one potential meetlocation by a corresponding potential meet time; electronicallycommunicating with a service provider computing entity associated withone of the one or more eligible service providers to engage the serviceprovider to deliver the item to the alternative destination;transmitting one or more signals to the delivery vehicle indicating ameet location and corresponding meet time identified as one of the oneor more potential meet locations for which the service provider iscapable of traveling to by the corresponding potential meet time; andtransferring the item to the service provider based on the meet locationand meet time.
 2. The method of claim 1, further comprising usingidentity verification data configured to enable a virtual handshakebetween the delivery vehicle and the service provider computing entitycarried by the service provider.
 3. The method of claim 1, furthercomprising: receiving data indicating that the item has been transferredto the service provider; and monitoring the location of the serviceprovider while the service provider transports the item.
 4. The methodof claim 1, wherein the service provider computing entity is a mobilecomputing entity carried by a service provider operator associated witha service provider vehicle.
 5. The method of claim 1, wherein monitoringthe location of one or more service providers comprises: querying adatabase of item data corresponding to a plurality of items to identifycharacteristics of the item; querying a database of available serviceproviders based at least in part on a portion of the characteristics ofthe item to identify one or more service providers qualified to deliverthe item to the alternative destination; and monitoring the location ofone or more service providers qualified to deliver the item to thealternative destination.
 6. The method of claim 1, wherein the methodfurther comprises transmitting the meet location and the correspondingmeet time to a the mobile computing entity carried by the serviceprovider.
 7. A system for engaging a service provider to perform alocation-specific service involving an item, the system comprising oneor more memory storage areas and one or more computer processors, thesystem configured to: receive a request to deliver an item located on adelivery vehicle traversing an assigned vehicle route to an alternativedestination, wherein an initial destination for the item is on theassigned vehicle route; in response to determining that an amount ofadditional energy the delivery vehicle would expend by altering theassigned vehicle route to deliver the item to the alternativedestination is greater than a threshold amount of energy, initiate aplan to handoff the item to a service provider for delivery to thealternative destination; monitor, based at least in part on locationdata received from the delivery vehicle, a location of the deliveryvehicle; monitor a location of one or more service providers; identifyone or more potential meet locations and corresponding potential meettimes; compare the location of one or more service providers against theone or more potential meet locations and corresponding meet times toidentify one or more eligible service providers, wherein the one or moreeligible service providers are identified as capable of traveling to atleast one potential meet location by a corresponding potential meettime; electronically communicate with a service provider computingentity associated with one of the one or more eligible service providersto engage the service provider to deliver the item to the alternativedestination; transmit one or more signals to the delivery vehicleindicating a meet location and corresponding meet time identified as oneof the one or more potential meet locations for which the serviceprovider is capable of traveling to by the corresponding potential meettime; and transfer the item to the service provider based on the meetlocation and meet time.
 8. The system of claim 7, further comprisingusing identity verification data configured to enable a virtualhandshake between the delivery vehicle and the service providercomputing entity carried by the service provider.
 9. The system of claim7, further configured to: receive transfer data indicating that the itemhas been transferred to the service provider; and monitor the locationof the service provider while the service provider transports the item.10. The system of claim 7, wherein the additional energy is fuelconsumed.
 11. The system of claim 7, wherein the transmitting one ormore signals to the delivery vehicle comprises transmitting one or moresignals to a mobile computing entity carried by a delivery vehicleoperator associated with the delivery vehicle.
 12. The system of claim7, wherein monitoring the location of one or more service providerscomprises: querying a database of item data corresponding to a pluralityof items to identify characteristics of the item; querying a database ofavailable service providers based at least in part on a portion of thecharacteristics of the item to identify one or more service providersqualified to deliver the item to the alternative destination; andmonitoring the location of one or more service providers qualified todeliver the item to the alternative destination.
 13. The system of claim7, wherein the method further comprises transmitting the meet locationand the corresponding meet time to a the mobile computing entity carriedby the service provider.
 14. One or more non-transitorycomputer-readable storage media having computer-readable program codestored therein, that, when executed by a computing device, cause thecomputing device to perform a method of engaging a service provider toperform a location-specific service, the method comprising: receiving arequest to deliver an item located on a delivery vehicle traversing anassigned vehicle route to an alternative destination, wherein an initialdestination for the item is on the assigned vehicle route; in responseto determining that the an amount of additional energy the deliveryvehicle would expend by altering the assigned vehicle route to deliverthe item to the alternative destination is greater than a thresholdamount of energy, initiating a plan to handoff the item to a serviceprovider for delivery to the alternative destination; monitoring, basedat least in part on location data received from the delivery vehicle, alocation of the delivery vehicle; monitoring a location of one or moreservice providers; identifying one or more potential meet locations andcorresponding potential meet times; comparing the location of one ormore service providers against the one or more potential meet locationsand corresponding meet times to identify one or more eligible serviceproviders, wherein the one or more eligible service providers areidentified as capable of traveling to at least one potential meetlocation by a corresponding potential meet time; electronicallycommunicating with a service provider computing entity associated withone of the one or more eligible service providers to engage the serviceprovider to deliver the item to the alternative destination;transmitting one or more signals to the delivery vehicle indicating ameet location and corresponding meet time identified as one of the oneor more potential meet locations for which the service provider iscapable of traveling to by the corresponding potential meet time; andtransferring the item to the service provider based on the meet locationand meet time.
 15. The non-transitory computer-readable storage media ofclaim 14, further comprising using identity verification data configuredto enable a virtual handshake between the delivery vehicle and theservice provider computing entity carried by the service provider. 16.The non-transitory computer-readable storage media of claim 14, furthercomprising: receiving data indicating that the item has been transferredto the service provider; and monitoring the location of the serviceprovider while the service provider transports the item.
 17. Thenon-transitory computer-readable storage media of claim 14, whereintransmitting one or more signals to the delivery vehicle comprises stepsfor transmitting one or more signals to a mobile computing entitycarried by a delivery vehicle operator associated with the deliveryvehicle.
 18. The non-transitory computer-readable storage media of claim14, wherein monitoring the location of one or more service providerscomprises: querying a database of item data corresponding to a pluralityof items to identify characteristics of the item; querying a database ofavailable service providers based at least in part on a portion of thecharacteristics of the item to identify one or more service providersqualified to deliver the item to the alternative destination; andmonitoring the location of one or more service providers qualified todeliver the item to the alternative destination.
 19. The non-transitorycomputer-readable storage media of claim 14, wherein the method furthercomprises transmitting the meet location and the corresponding meet timeto a the mobile computing entity carried by the service provider. 20.The non-transitory computer-readable storage media of claim 14, whereinthe additional energy is fuel consumed.